Telecommunications Addressing System and Method

ABSTRACT

A telecommunications addressing system/method allowing selection of a telephone instrument device (TID) using arbitrary identifiers is disclosed. The system/method allows a source TID (STD) to select a target TID (TTD) by the use of a Target Telephone Identifier (TTI) data string rather than a traditional numeric telephone identification (NTI). This TTI is then indexed within a TTI/NTI mapping server (TMS) that functions as a hierarchical repository of TTI/NTI mappings. STD/TTD communication is established by first performing a lookup of the STD-selected TTI within the TMS to identify the NTI of the TTD. Once the NTI of the STD has been identified by the TMS, communication between the STD and TTD is established using the NTI via the normal public switched telephone network (PSTN). TMS TTI lookup may be performed via STD TID web application and/or via PSTN infrastructure interface.

CROSS REFERENCE TO RELATED APPLICATIONS U.S. Provisional PatentApplications

This application claims benefit under 35 U.S.C. §119 and incorporates byreference United States Provisional Patent Application for SMARTTELECOMMUNICATIONS INTERFACE AND SYSTEMS by inventor Maqsood A. Thange,filed electronically with the USPTO on Nov. 29, 2012, with Ser. No.61/731,009, EFS ID 14335607, confirmation number 1093, docketCZMTH.00002.

This application claims benefit under 35 U.S.C. §119 and incorporates byreference United States Provisional Patent Application for SMARTTELECOMMUNICATIONS INTERFACE AND SYSTEMS by inventor Maqsood A. Thange,filed electronically with the USPTO on Dec. 3, 2012, with Ser. No.61/732,585, EFS ID 14367194, confirmation number 6174, docketCZMTH.00002P2.

PARTIAL WAIVER OF COPYRIGHT

All of the material in this patent application is subject to copyrightprotection under the copyright laws of the United States and of othercountries. As of the first effective filing date of the presentapplication, this material is protected as unpublished material.

However, permission to copy this material is hereby granted to theextent that the copyright owner has no objection to the facsimilereproduction by anyone of the patent documentation or patent disclosure,as it appears in the United States Patent and Trademark Office patentfile or records, but otherwise reserves all copyright rights whatsoever.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not Applicable

REFERENCE TO A MICROFICHE APPENDIX

Not Applicable

FIELD OF THE INVENTION

Embodiments of the present invention generally relate to systems andmethods for identifying and targeting communication with atelecommunications device within a general public switched telephonenetwork (PSTN). While not limitive of the invention teachings, thepresent invention may in some circumstances be advantageously applied tocategories including U.S. Patent Classifications 370/352; 379/88.17;379/90.01; 379/201.05; 379/201.07; 379.218.011 370/265.09; 379/900; and455/550+.

PRIOR ART AND BACKGROUND OF THE INVENTION Overview

With respect to conventional telecommunication devices operating withinthe public switched telephone network (PSTN), the use of numerictelephone numbers (numeric telephone identifier (NTI)) that uniquelyaddress a target telecommunication device (TTD) is standardized. Thespecific format, length, and interpretation of these telephone numbersis often equipment dependent and often dependent on the country in whichthe TTD is located and/or dependent on the country in which the sourcetelecommunication device (STD) is located.

While most smartphone and other intelligent STDs have made attempts tosimplify the association of a TTD with their respective NTI usingsoftware implementing telephone “address books” and the like, thisapproach is insufficient to account for changes in TTD/NTI associationsdue to external events (phone numbers change, area codes change, changesin PBX extensions, etc.). Other attempts to make TTD associations usingan Internet address (as in U.S. Pat. No. 7,382,871 for CALL SETUP USINGA PACKET-SWITCHED ADDRESS SUCH AS AN INTERNET ADDRESS OR THE LIKE issuedto Michael J. Ure on Jun. 3, 2008) or to integrate the STD into theInternet infrastructure (as in U.S. Pat. No. 6,169,734 for INTERNETtelephone SET issued to James E. Wilson on Jan. 2, 2001) have provenunsuccessful in addressing a number of issues relating to the use ofNTIs within the PSTN. These deficiencies have become more pronounced asthe PSTN infrastructure increases with the use of wireless and mobiletelephones, smartphones, tablet computers, and telephone enabledpersonal computers (laptops, desktops, etc.).

PRIOR ART DEFICIENCIES

From the above discussion and an inspection of the prior art in thefield, it can be discerned that the use of NTIs within the PSTN suffersfrom the following disadvantages:

-   -   Phone numbers are cryptic, difficult to remember, easy to        forget. This confusion is exacerbated by the use of country        codes, city codes, and constantly changing area codes within the        NTI infrastructure.    -   Phone Numbers are fixed digits 0-9 and have no flexibility for        change based on consumer input. Telephone numbers are generally        10 digits long, including the area code. Adding the country        code, city code, the local telephone number can be as long as 15        characters or more.    -   For international calls, some countries use a 011 prefix to        dial, some use 1, while Indian callers use 00. This is very        confusing for most people, especially for travelers and the        elderly. In an attempt to somehow make sense out of these        confusing digits, telephone companies separate the digits using        parentheses, spaces, and dashes (e.g., (999) 999-9999). However,        these formats are country specific.    -   Telephone companies are constantly fighting for each other's        business and as a result, telephone numbers associated with        these companies also change constantly.    -   In the current environment of telephone number usage, whenever a        telephone company runs out of digits, they add a prefix digit,        start a new area code and make a public announcement. For        example, New Jersey for a long time had a 201 area code. When        they ran out of telephone numbers under 201, some numbers were        changed to a 908 area code and when they ran out of telephone        numbers again a 908 area code was added, with a further change        occurring later to introduce a 732 area code. Similar changes        have occurred in other states and countries too. When this        happens, the public is forced to change their telephone diaries        and speed dials while corporations are forced to change their        telephone directories, websites, letterhead, and product        documentation. Those who are unaware of the change (usually        overseas callers or infrequent callers) keep on dialing the        wrong number till somehow they find out the real reason of why        their call is not going through.    -   Most of the times people are forced to change their telephone        numbers when they change their residence or business location.        Similarly, every time they change jobs their work telephone        number also changes. When this happens, these people cannot be        reached unless their new cryptic telephone numbers are        publicized again to those who wish to contact them. While some        prior art methodologies have suggested using identifiers        maintained by the telephone company that are portable within the        context of the telephone company's infrastructure, this        technique will not work if the user changes their residence        country or telephone company.    -   Many people have multiple telephone numbers for multiple uses        (home telephone, cell telephone, fax number, work number,        emergency number, and a telephone number for a vacation home,        etc.). Callers have to remember each number separately or        maintain a diary. Almost always these numbers have no similarity        with each other.    -   Phone numbers are allocated by telephone companies. The public        has little or no say about what the telephone number should be.        The entire process of who gets what telephone number is        controlled by telephone companies.    -   Use of telephone numbers provides very little functionality to        individuals and businesses. Since telephone companies control        these mappings consumers also have to pay significant amount of        money for specific telephone numbers. For example, a telephone        number which translates into a business name on telephone keypad        such as “1800flowers”.        To date the prior art has not fully addressed these        deficiencies.

OBJECTIVES OF THE INVENTION

Accordingly, the objectives of the present invention are (among others)to circumvent the deficiencies in the prior art and affect the followingobjectives:

-   -   (1) Provide for a telecommunications addressing system and        method that allows for consumers to assign arbitrary identifiers        to numeric telephone numbers.    -   (2) Provide for a telecommunications addressing system and        method that allows for consumers to control the addressing of        their telephones.    -   (3) Provide for a telecommunications addressing system and        method that allows for consumers to configure call blocking on        their telephones.    -   (4) Provide for a telecommunications addressing system and        method that allows for automatic reconfiguration of area codes        or other information related to numeric telephone identifiers.    -   (5) Provide for a telecommunications addressing system and        method that allows for synching of telephone numbers to        calendars.    -   (6) Provide for a telecommunications addressing system and        method that allows for conditional dialing of telephone numbers        based on a number of conditional events.    -   (7) Provide for a telecommunications addressing system and        method that allows for telephone identifiers to be descriptive        of the telephone user.    -   (8) Provide for a telecommunications addressing system and        method that allows for trees of telephone numbers to be        associated with an individual or corporate entity.    -   (9) Provide for a telecommunications addressing system and        method that allows for automated navigation of voice menu        systems with predefined menu traversal scripts.    -   (10) Provide for a telecommunications addressing system and        method that allows for automated updating of corporate telephone        tree profiles without manual intervention from remote telephone        callers.

While these objectives should not be understood to limit the teachingsof the present invention, in general these objectives are achieved inpart or in whole by the disclosed invention that is discussed in thefollowing sections. One skilled in the art will no doubt be able toselect aspects of the present invention as disclosed to affect anycombination of the objectives described above.

BRIEF SUMMARY OF THE INVENTION System/Method Overview

The present invention relates to a system/method for choosing andcontrolling telephone identification by individuals and businesses. Thedisclosed system takes advantage of universal interactive programminglanguages (such as Java, J2ME, PERL or any cellphone programminglanguages such as BREW (and relational databases such as Oracle, DB2,MySQL, etc.)), the world-wide web, and/or the existing public switchedtelephone network (PSTN). Instead of using a conventional telephonenumber to identify a target telephone device (TTD), the presentinvention allows telephone subscribers to choose their own targettelephone identifier (TTI) to describe the numeric telephone identifier(NTI) of the target telephone. This present invention does not replacethe use of telephone numbers but rather serves as a layer of abstractionto the existing telephone numbers assigned by the telephone companies.The present invention permits telephone users to control this add-onwithout any involvement of the telephone companies.

General Invention Objective

The objective of this technology is to let the telephone subscriberschoose and maintain a more powerful and functionality enhanced TTIinstead of a numeric telephone number provided by the telephonecompanies. The TTI may be chosen and controlled by the telephone usersthemselves. Provisions within this architecture provide for global TTIdirectories that may be browsed and searched in a similar fashion tothat of web pages, but with additional levels of security andfunctionality that are directed to improving the maintainability of thetelephone directory infrastructure.

BRIEF DESCRIPTION OF THE DRAWINGS

For a fuller understanding of the advantages provided by the invention,reference should be made to the following detailed description togetherwith the accompanying drawings wherein:

FIG. 1 illustrates a preferred exemplary system embodiment of thepresent invention;

FIG. 2 illustrates a flowchart depicting a preferred exemplary methodembodiment of the present invention;

FIG. 3 illustrates a preferred exemplary alternate system embodiment ofthe present invention;

FIG. 4 illustrates a flowchart depicting a preferred alternate exemplarymethod embodiment of the present invention;

FIG. 5 illustrates an exemplary data flow diagram depicting integrationof a telephone user interface (TUI) within a STD and system componentssupporting remote loading of application software supporting features ofthe present invention;

FIG. 6 illustrates an exemplary BASIC INFORMATION dialog screen usefulin some preferred invention embodiments;

FIG. 7 illustrates an exemplary BLOCKED CALL dialog screen useful insome preferred invention embodiments;

FIG. 8 illustrates an exemplary GROUP PARTICIPATION dialog screen usefulin some preferred invention embodiments;

FIG. 9 illustrates a screen dialog depicting an exemplary telephone callinitiation data entry layout useful in some preferred inventionembodiments;

FIG. 10 illustrates a screen dialog depicting an exemplary telephonecall initiation data entry layout that shows a time dependentconditional TTI display option;

FIG. 11 illustrates a screen dialog depicting an exemplary telephonecall initiation data entry layout that shows a time dependentconditional TTI display option;

FIG. 12 illustrates a screen dialog depicting an exemplary telephonecall initiation data entry layout that shows selection of a “calling as”telephone profile;

FIG. 13 illustrates an exemplary call blocking system architecture basedon TTI/NTI mapping;

FIG. 14 illustrates a flowchart of an exemplary TTI call blockingmethodology useful in some preferred invention embodiments;

FIG. 15 illustrates an exemplary data flow diagram describing how TTIinformation is entered, validated, and stored within the TMD;

FIG. 16 illustrates a flowchart of an exemplary TTI validationmethodology useful in some preferred invention embodiments;

FIG. 17 illustrates an exemplary TTI hierarchical data structure (notethat the term hierarchical data structure should not be confused withvery old databases termed “Hierarchical Databases”; more advanceddatabases such as Oracle, DB2, etc. are termed relational databases);

FIG. 18 illustrates an exemplary TTI hierarchical data structuredepicting a geographic hierarchy;

FIG. 19 illustrates an exemplary TTI hierarchical data structuredepicting localized control of a TTI branch;

FIG. 20 illustrates an exemplary TTI search path hierarchy;

FIG. 21 illustrates an exemplary TTI search path hierarchy incorporatinga TTI entry managed by a third party;

FIG. 22 illustrates an exemplary TTI search path hierarchy incorporatinga TTI entry managed by a third party secured with an Access Control List(ACL);

FIG. 23 illustrates an exemplary system embodiment incorporatingoutgoing call screening;

FIG. 24 illustrates an exemplary system embodiment incorporatingincoming call screening;

FIG. 25 illustrates an exemplary system block diagram depictingintegration of TTI/NTI data within enterprise websites and the gatheringof this data by a global TTI/NTI mapping server operating as a webcrawler;

FIG. 26 illustrates an exemplary TTI/NTI tree structure;

FIG. 27 illustrates an exemplary TTI/NTI navigation screen suitable fora typical mobile communication device;

FIG. 28 illustrates examples of TTI/NTI mapping information beingincorporated within HTML metadata;

FIG. 29 illustrates an exemplary TTI/NTI metadata definition grammar;

FIG. 30 illustrates variations in the types of NTI atomic types that maybe used in a variety of preferred invention embodiments;

FIG. 31 illustrates a flowchart depicting exemplary methods to extractTTI/NTI mapping data from enterprise databases and present thisinformation as metadata within an enterprise website for later scanningby a web crawler;

FIG. 32 illustrates an exemplary web crawler application that may beused to scan HTML web pages containing TTI/NTI mapping information topopulate a TTI/NTI mapping database (TMD);

FIG. 33 illustrates an exemplary system capable of populating the TMDusing information gathered by searching websites for HTML containingvalid telephone numbers;

FIG. 34 illustrates an exemplary method flowchart detailing thepopulating of the TMD using information gathered by searching websitesfor HTML containing valid telephone numbers;

FIG. 35 illustrates an exemplary system capable of populating the TMDusing information gathered by searching social media websites for HTMLcontaining valid telephone numbers;

FIG. 36 illustrates an exemplary method flowchart detailing thepopulating of the TMD using information gathered by searching socialmedia websites for HTML containing valid telephone numbers;

FIG. 37 illustrates an exemplary system block diagram depicting apresent invention preferred exemplary embodiment incorporating STDTTI/NTI mapping cache;

FIG. 38 illustrates a flowchart depicting an exemplary STD TTI/NTImapping cache method;

FIG. 39 illustrates a preferred exemplary invention system embodimentapplied to automated telecom updating of TTI/NTI mappings based on telcooperator input and/or input from telecom standards organizations;

FIG. 40 illustrates a flowchart depicting a preferred exemplaryinvention method embodiment applied to automated telecom updating ofTTI/NTI mappings based on telco operator input and/or input from telecomstandards organizations;

FIG. 41 illustrates a preferred exemplary system embodiment implementingreverse callback addressing;

FIG. 42 illustrates a preferred exemplary method embodiment implementingreverse callback addressing;

FIG. 43 illustrates a preferred exemplary method embodiment implementingoptimized addressing with a view to reducing telephone charges;

FIG. 44 illustrates a preferred exemplary system embodiment implementingqueued forward call processing;

FIG. 45 illustrates a preferred exemplary system embodiment implementingqueued reverse call processing;

FIG. 46 illustrates a flowchart depicting a preferred exemplary methodembodiment implementing queued call processing;

FIG. 47 illustrates an exemplary user interface depicting a TTD incomingcall queue prioritization display;

FIG. 48 illustrates an exemplary user interface depicting an STDoutgoing call queue status display;

FIG. 49 illustrates a preferred exemplary system embodiment illustratingintegration of call processing with calendaring software;

FIG. 50 illustrates an exemplary user interface screen depictingintegration of calendaring software into the call processing function;

FIG. 51 illustrates a preferred exemplary system embodiment whereintelephone call processing is interfaced to existing host softwareapplications on a computing device;

FIG. 52 illustrates an exemplary parental control/call restrictionsdefinition user interface dialog;

FIG. 53 illustrates an exemplary parental control/call restrictionsmethod;

FIG. 54 illustrates a preferred exemplary system embodimentincorporating GPS location tracking;

FIG. 55 illustrates a preferred exemplary method embodimentincorporating GPS location tracking;

FIG. 56 illustrates a preferred exemplary TTD dialog incorporating GPSlocation tracking;

FIG. 57 illustrates an exemplary system embodiment incorporating TTIreverse lookup capability;

FIG. 58 illustrates an exemplary method embodiment incorporating TTDreverse lookup capability;

FIG. 59 illustrates an exemplary method embodiment incorporating STDreverse lookup capability;

FIG. 60 illustrates an exemplary system embodiment incorporatingoutgoing message (OGM) capability;

FIG. 61 illustrates an exemplary method embodiment incorporatingoutgoing message (OGM) capability;

FIG. 62 illustrates an exemplary user interface dialog supportingoutgoing message (OGM) capability;

FIG. 63 illustrates an exemplary system embodiment incorporatingmultiple mapping servers;

FIG. 64 illustrates multiple mapping databases.

DESCRIPTION OF THE PRESENTLY PREFERRED EXEMPLARY EMBODIMENTS

While this invention is susceptible of embodiment in many differentforms, there is shown in the drawings and will herein be described indetailed preferred embodiment of the invention with the understandingthat the present disclosure is to be considered as an exemplification ofthe principles of the invention and is not intended to limit the broadaspect of the invention to the embodiment illustrated.

The numerous innovative teachings of the present application will bedescribed with particular reference to the presently preferredembodiment, wherein these innovative teachings are advantageouslyapplied to the particular problems of a TELECOMMUNICATIONS ADDRESSINGSYSTEM AND METHOD. However, it should be understood that this embodimentis only one example of the many advantageous uses of the innovativeteachings herein. In general, statements made in the specification ofthe present application do not necessarily limit any of the variousclaimed inventions. Moreover, some statements may apply to someinventive features but not to others.

Telephone not Limitive

The present invention will use the term “telephone”, “phone”, and theirderivatives to broadly cover any communications device that may beconfigured to operate within the context of a public switched telephonenetwork (PSTN). This may include cellular telephones, mobile telephones,and conventional wired telephone (landline, VOIP phones, etc.)infrastructures.

Telephone Number not Limitive

The present invention will use the term “telephone number”, “NTI”, andtheir derivatives to broadly cover any identification methodology usedwithin the a public switched telephone network (PSTN) to uniquelyidentify a telephone or telephone branch exchange. This use generallyrelates to numeric telephone numbers “0123456789” but is anticipated tocover other non-numeric identifiers that may be used within a PSTN inthe future.

Source/Target Telephone Identifiers (STI/TTI) not Limitive

The present invention will use the term “source telephone identifier(STI)” to generally reference a telephone identifier associated with atelephone call originator and “target telephone identifier (TTI)” togenerally reference a telephone identifier associated with a telephonecall recipient. However, in many circumstances the term “TTI” maygenerally refer to any form of telephone identifier used to perform alookup to resolve a numeric telephone identifier (NTI) (conventionaltelephone company telephone number). For example the “TTI/NTI mappingdatabase (TMD)” referenced herein is generally used to match TTIidentifiers to their respective NTI resolved PSTN telephone numbers.However, the TMD may be used to resolve STIs if used by the telephonecall receiver. Thus, the term “TTI” may in some cases be synonymous withSTI and be dependent on the discussion context.

TTI Encoding not Limitive

The present invention will use the term “target telephone identifier(TTI)” and its derivatives to broadly cover any data string (includingbut not limited to alphanumeric text strings, binary data streams (offixed and/or varying bit widths, etc.) that may be used as an identifierfor the target telephone instrument device (TTD). Within this contextthe term “alphanumeric text string” may include any combination of alphaand/or numeric symbols selected from traditional character encodingtables such as ASCII, EBCDIC, BAUDOUT, that are typically associatedwith 5-8 bit alphabetic/numeric character encodings, but may alsoinclude encoding methodologies such as UNICODE (UCS-2, UTF-8, UTF-16,etc.) that permit representation of more complex character setsassociated with foreign languages that are not necessarily representableusing traditional 5-8 bit character encodings.

TTI Data Entry not Limitive

The present invention may use a wide variety of methodologies to enterdata associated with the TTI, including but not limited tokeyboard/keypad entry and/or voice recognition techniques. Additionally,some preferred embodiments may incorporate telephonetic voice data entryto allow character-by-character entry of the TTI. Within this context ofany of these data entry techniques the use of auto-completion (matchingagainst previously entered or known TTI entries associated with a localand/or remote cache is anticipated within the present invention scope.

NTI Encoding not Limitive

The present invention may use a wide variety of methodologies to encodenumeric telephone identifiers (NTIs). While conventional telephonenumber strings incorporating conventional formats (e.g. “(555)123-4567”; “555-123-4567”; “555.123.4567”) are anticipated, the NTIwithin the context of the present invention may incorporate otherfeatures in some circumstances including but not limited to thefollowing:

-   -   Numeric paths (call sequencing information) to navigate through        a DTMF-driven voice menu system (e.g., “555-123-4567/1/2/3/9”        for selection of “9” after sequentially passing through menu        options “1”, “2”, and “3”;    -   Call extension processing to select specific extensions from a        given main PBX number (e.g., “555-123-4567 x123” for selection        of extension “123” after call pickup at the main number        “555-123-4567”;    -   Call sequence redirection on the detection of a busy signal or        unavailability of the telephone call recipient (e.g.,        “555-123-4567 {x123, x456}” to first attempt connection at        extension “x123” and if unavailable, reconnect to extension        “x456”.        One skilled in the art will recognize that this list of NTI        modifiers is non-exhaustive and only exemplary of a wide variety        of NTI content and syntax that may be implemented using the        teachings of the present invention. Thus the term “NTI” and its        variants should be broadly interpreted to encompass more than        just strictly numeric telephone numbers as typically dialed        using a PSTN connected telephone.

TTI Composition not Limitive

TTIs within the context of the present invention may incorporate anycombination of letters, digits, and/or symbols and may permit consumersto choose imaginative ways to identify themselves (e.g., JohnLawyer,NYLawyerone, Jim53, TallJim). The TTI identifiers are not limited to anysymbol length restriction such as is currently present in traditionaltelephone numbers.

Call Blocking not Limitive

While many preferred invention embodiments may implement call blockingfunctionality (blocking outgoing calls from the STD to the TTD and/orblocking incoming calls to the TTD from the STD), the invention alsoanticipates situations where the call “blocking” incorporates anautomatic transfer of the call to voicemail. This voicemail answeringsystem may incorporate TTI-indexed messages that are specific to the STDcaller or TTD recipient.

TMS/TMD Configurations not Limitive

While the present invention disclosure depicts a single TMS/TMDserver/database structure, the present invention is not limited to thisconfiguration and may in some implementations be applied to scenarioshaving multiple TMS and/or TMD elements. These configurations mayprovide for replicated TMD information or segmented TMD data dependingon application. Multiple TMS servers may also be utilized to improveaccess time performance to the TMD data relative to a given STD/TTDservice request.

Method Steps not Limitive

The general method steps described herein may be modified heavilydepending on a number of factors, with rearrangement and/oraddition/deletion of steps anticipated by the scope of the presentinvention. Integration of the described methods and other preferredexemplary embodiment methods in conjunction with a variety of preferredexemplary embodiment systems described herein is anticipated by theoverall scope of the present invention.

Computing Device not Limitive

The present invention may utilize the term “computer system”, “computingdevice (CD)” or its equivalent in describing various control systemsused within the present invention. These synonymous terms should begiven their widest possible interpretation in this context, and arespecifically anticipated to include mobile/portable computing devicessuch as handheld computers, tablet computers, smartphones, cellphones,laptop computer, and the like.

Cross-Information not Limitive

The present invention may permit a wide variety of cross-information tobe communicated between the STD and the TTD during telephone callinitiation and/or processing. This may include text messages,photographs, video clips, sound recordings, voice recordings, etc. Thus,cross-information exchanges between the STD and TTD should beinterpreted broadly within this context.

Embodiments are Exemplary

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the disclosed and/or claimed embodiments.Further features and/or variations may be provided in addition to thoseset forth herein. For example, the disclosed embodiments may be directedto various combinations and subcombinations of the disclosed featuresand/or combinations and subcombinations of several further featuresdisclosed below in the detailed description.

System Overview (0100)

An overview of a presently preferred exemplary system embodiment isgenerally illustrated in FIG. 1 (0100) wherein the system incorporates amapping server (TMS) (0111) that indexes an arbitrary user-definedtarget telephone identifier (TTI) with an associated numeric telephoneidentification (NTI) (telephone number). The TTI/NTI mapping server(TMS) executes machine instructions on a computer system that areretrieved from a computer readable medium (0112). A relational orhierarchical database (TMD) (0113) of TTI/NTI mappings (0114) isutilized to allow a given TTI to serve as the lookup index for aresolved NTI telephone number (or numbers) associated with the TTI.

Within this framework, a computer network (0101) connects a sourcetelephone device (STD) (0120) (typically executing machine instructionsretrieved from a computer readable medium (0121)) and the TMS (0111)that enables the STD to initiate requests (0122) for TTI/NTI translationto the TMS (0111). These TTI requests (0122) are then translated by theTMS (0111) to a resolved NTI (or a tree of potential NTIs) and returned(0123) to the STD (0120) for processing. Once the user has selected thedesired TTI/NTI mapping from the potential candidates returned (0123) bythe TMS (0111), the STD initiates a telephone call (0124) via the publicswitched telephone network (0140) using internal software on the STD(0120). The telephone call is then routed (0134) by the PSTN (0140) tothe target telephone device (TTD) (0130) identified by the NTI. The callis continued and completed (0141) using the PSTN (0140).

While the TTD (0130) need not be a web-enabled smart telephone, if itdoes possess this capability it will typically execute machineinstructions read from a computer readable medium (0131) and mayinitiate requests (0132) to the TMS (0111) prior to or during the callcompletion (0141) to request the source telephone identifier (STI) ofthe STD (0120) and/or its associated NTI. This information as returned(0133) by the TMS (0111) can be used to maintain a local cache ofreceived caller information that may be used to return calls to the STDat a later time.

The TMD (0113) may incorporate additional mapping structures toassociate initiated telephone calls from the STD (0120) to the TTD(0130) such that the internal TTIs associated with the STD (0120) andTTD (0130) are linked so that a locality of reference (intersection ofcontext) can be defined between the STD (0120) and TTD (0130). Thispermits subsequent TTI requests (0122) by the STD (0120) referencingTTDs that are related to the TTD (0130) to be positioned at the top of asearch list presented to the STD (0120).

It should be noted as detailed elsewhere herein that the STD (0120) andTTD (0130) represent arbitrary telecommunications devices and need notnecessarily be mobile telephones. Land lines, tablets, and other liketelecommunication devices are anticipated as being compatible with thisTTI/NTI mapping infrastructure.

Method Overview (0200)

A method associated with the system depicted in FIG. 1 (0100) isgenerally illustrated by the flowchart in FIG. 2 (0200) and comprisesthe following steps:

-   -   (1) The Call Originator (CO) enters the target telephone        identifier (TTI) for the Call Receiver (CR) on a source        telephone (telephone instrument device (TID)) (STD) (0201).    -   (2) The STD sends the TTI along with other relevant details such        as the caller's TTI and password to the telephone mapping server        (TMS) (0202).    -   (3) The TMS sends back the numeric telephone identifier (NTI)        (telephone number, and possibly other information objects such        as pictures, logo, short messages, GPS location, GPS location        translation, etc.) to the STD (0203).    -   (4) STD dials the NTI to connect the CO STD and the target TID        (TTD) associated with the CR (0204).    -   (5) The telephone call is routed through the public switched        telephone network (PSTN) through the telephone company central        office (CCO) to the TTD associated with the CR (0205).    -   (6) CR (if properly equipped with application specific software)        may optionally connect to TMD and get CO info such as CO TTI,        picture/logo, GPS location, GPS location translation, etc.        (cross-information transmission between STD and TTD may be        implemented) (0206).        It should be noted that STD callback in this context may be used        by the TMS (0111) to force the STD (0120) to dial more than one        TTD (0130) to initiate conference calls and the like. The TTD        may or may not be wireless or web-enabled telephone in order to        receive calls using TTI addressing. Additionally, if the CO is        aware that the NTI has not changed since the last time the CR        has been telephoned, then application software on the STD may be        configured to skip steps (1)-(3) by accessing a TTI/NTI cache        within the STD and if the CR NTI changes then TMS can push or        update those STDs which have previously used the CR NTI. In this        scenario software resident on the STD can retrieve the NTI from        internal memory of the STD without any need to connect to the        TMS. As indicated in the method, the TMS incorporates        appropriate security measures to ensure authorized access to the        TTI/NTI mapping information stored on the TMS.

Alternate System Overview (0300)

The exemplary system embodiment as generally illustrated in FIG. 1(0100) may be embodied in an alternate form as depicted in FIG. 3 (0300)wherein the STD (0320) interfaces with the PSTN (0340) (and theassociated telephone company central office (CCO)) using a transparentTTI interface that provides the PSTN (0340) with the TTI data stream(0324) identifying the TTD (0330). This TTI is then indexed using theTMS (0311) by the telephone company central office (CCO) using request(0322)/return (0323) communications with the TMS (0311) and thecorresponding TMD (0313) to retrieve the TTI/NTI mapping (0314). Oncethe telephone company has resolved the NTI from the STD-supplied TTI,the call is routed (0334) to the STD (0330). STD caller information(0332) may be requested of the STD (0320) and the returned TTI/NTIinformation (0333) passed along to the TTD (0330) for use in a laterreturn call to the STD (0320).

This scenario also permits the CR to connect to connect to the TMD andretrieve CO info such as CO identifier, picture/logo, GPS location, GPSlocation translation, etc. Thus, information may be bi-directionallytransferred between the call originator (CO) and call recipient (CR).

Alternate Method Overview (0400)

An alternate method associated with the alternate system depicted inFIG. 3 (0300) is generally illustrated by the flowchart in FIG. 4 (0400)and comprises the following steps:

-   -   (1) The Call Originator (CO) enters the target telephone        identifier (TTI) for the Call Receiver (CR) on a source        telephone (telephone instrument device (TID)) (STD) (0401).    -   (2) The STD sends the TTI along with other relevant details such        as the caller's TTI and password to the telephone company        (0402).    -   (3) The telephone company sends the TTI information to a        telephone mapping server (TMS) (0403).    -   (4) The TMS sends back the numeric telephone identifier (NTI)        (telephone number) to the telephone company (0404).    -   (5) The telephone company uses the NTI to route (connect) the        call between the CO STD and the target TID (TTD) associated with        the CR through the public switched telephone network (PSTN)        (0405).    -   (6) CR (if properly equipped with application specific software)        may optionally connect to TMD and get CO info such as CO TTI,        picture/logo, GPS location, GPS location translation, etc.        (cross-information transmission between STD and TTD may be        implemented) (0406).        It should be noted that the TTD may or may not be wireless or        web-enabled telephone in order to receive calls using TTI        addressing. As indicated in the method, the TMS incorporates        appropriate security measures to ensure authorized access to the        TTI/NTI mapping information stored on the TMS.

System Integration (0500)

The present invention anticipates a wide variety of system integrationcontexts, but a preferred exemplary system application context isgenerally illustrated in FIG. 1 (0100) wherein the STD (0520) (and/orTTD) executes software read from a computer readable medium (0521) thatmay include a core operating system (0522) in addition to operatingsystem application programming interface (API) (0523) supportingtelephone dialing/call processing functions. This API (0523) is used asthe software application platform for a telephone user interface (TUI)(0524) application that embodies the present invention functionalitywith respect to interactions with the TTI/NTI mapping server (TMS)(0511) and the PSTN.

Loading of the TUI (0524) on the STD (0520) (and/or TTD) is typicallyaccomplished by communication with the TMS (0511) over a computernetwork (0501) using a website interface (0514) to access a softwareapplication (APP) database storage (APS) (0514) to retrieve theparticular software application components constituting the TUI (0524).Control of this application downloading function within the TMS (0511)is typically governed by software executed within the TMS (0511) that isretrieved from a computer readable medium (0512). While the TMS (0511)is generally illustrated in FIG. 5 (0500) as the source for the TUI(0524) application software, one skilled in the art will recognize thatother APP servers may be utilized to accomplish this function apart fromthe TTI/NTI mapping function normally performed by the TMS (0511).

It should be noted that the TUI (0524) illustrated in FIG. 5 (0500) isshown as implemented within the context of user application softwarethat is loaded from a remote database (0514), but could equally beimplemented as integrated telephone functionality within the OS APIinterface (0523) and/or the core STD operating system (0522).

TTI Search Methodologies

The present invention permits an individual TTI subscriber to useweb-page registration of TTIs and enter a TTI-associated NTI to enabledefined classes or groups of individuals to make simple telephone callsusing TTIs rather than initiating call processing using a traditionalNTI.

A more sophisticated application where corporations are able to maintaintheir entire list of telephones in a universally structured way indirectory tree (like file/folder directory tree on computer) under theircorporate TTI is also possible. For example, suppose that Sony has a TTIcalled ‘Sony’ under this TTI they list their entire list of GroupParticipant's TTIs. Callers will be able to browse/search through acompany's TTI list to reach a specific person or a department ratherthan go through the slow and annoying voice menus as currently used.

An originating caller will enter a TTI using QWERTY keys or numerickeypad for forming an alphanumeric TTI (just as the text messages arewritten). When a TTI user dials a TTI, the software on caller'stelephone first makes a very quick and short connection to the globalTTI server either thru Internet or any other network including thenetwork used by the telephone companies to make call. Using the callreceiver's TTI as the identifier, the software retrieves the telephonenumber. Based on the comparison of caller's area code, city code andcountry code, and call receiver's area code, city code and country,software on the TMS concatenates appropriate prefixes to form the finaldialing number string. Then software on the server sends the NTI to thecaller's telephone and then the TTI software on caller's telephone dialsthe actual telephone number, or if the telephone company has directaccess to the TMS then the company can directly retrieve the telephonenumber associated with the name and dial the telephone number oncaller's behalf without sending it to the caller's telephone and forcingthe software on the caller's telephone to dial the number.

Static vs. Dynamic Call Routing

Currently corporations do use telephone numbers and assign it a name(e.g., 1800flowers). However, these names are tied to fixed telephonenumbers (i.e., 1800flowers=1-800-356-9377). If this telephone numberchanges or if there is a need to add extra digit to the existingtelephone number then the name 1800flowers cannot be used to refer tothe new number. In this case the assignment of the name to the number isstatic. However, by using the TTI technology, no matter how many timesthe telephone number changes, the new number can be assigned to the sameTTI without changing the name. According to the teachings of the presentinvention, the TTI mapping assignment is Dynamic.

Phasing Out the Dialing of Telephone Numbers

The present invention allows an individual or corporation to maintaintheir TTIs and assign one or more telephone numbers to their TTIs atwill. This approach brings all the people of the world together in oneglobal community. This can be done without obstructing the telephonecompanies' current use of telephone numbers. Telephone companies willcontinue to use telephone numbers at the telephone exchange as dialingcodes. However, the public need not be tied to the standards defined bythe telephone companies. Initially, people will continue to maketelephone calls using TTIs and telephone numbers. However, the presentinvention makes it possible for explicit NTI usage to be phased out orto be used as a secondary (more primitive) method of initiatingtelephone calls.

Changes in Sub-Area Code, City Code, or Country Code

The present invention permits the TMS Administrator or the telephonecompanies to change the actual telephone numbers associated with theTTIs with ease and without the need to bother the subscribers. They candirectly make a mass update to the TTI database by computer software andmake corrective changes to those telephone numbers that require changes.In other words, telephone numbers associated with the TTIs can bechanged by the telephone companies in case of area code change, citycode changes etc. Those TTI users can be informed of this change bysoftware-generated email or by text or voice message just as a simplenotification rather than a massive public advisory. This does notrequire change of habit on the public's part. There are no missed calls,wrong numbers, etc. The public will seamlessly continue to dial the sameTTIs which they used to dial before the mass update done by thetelephone company and the global TTI server will simply provide thelatest telephone number associated with the TTI.

TTI Nickname Assignment

When a TTI is displayed on a TTD, the call recipient may assign the STDhis/her own nickname, store this nickname on a TMS account and later usethe nickname to dial the STD. When the call is made using the nicknamethe TTI server uses the nickname from caller's account to lookup theactual TTI then lookup the telephone number and then dial the TTI. Forexample, Mr. John Smith has a TTI is Jsmithlovesfishing. He hasdistributed his TTI to all his friends and business associates asJsmithlovesfishing. They dial his TTI as Jsmithlovesfishing. However,his son Mark Smith whose TTI is MarquiMark need not dialJsmithlovesfishing to call his father. Mark Smith can simply assign anickname called “Great Dad” to TTI Jsmithlovesfishing under his TTIaccount MarquiMark. When Mark dials the TTI Great Dad, the TTI server,first checks his account's nickname section to fetch the TTI associatedwith “Great Dad” which is Jsmithlovesfishing, then retrieves thetelephone number associated with Jsmithlovesfishing. In case if TTIserver not finding the nickname then it will assume that “Great Dad” isa TTI and dial “Great Dad” as a TTI. This example illustrates therecursive nature of TTI/NTI mapping resolution.

Nicknames need not be globally unique as are TTIs. However, they must beunique for all the TTIs assigned to a telephone number. Multiplesubscribers each with different telephone number can give may providethe same nickname.

For example, when calling a doctor, the call originator need not dialthe TTI provided by the doctor (e.g., InternistInPrinceton). The calloriginator see the doctor as ‘Primary Care Physician’. The calloriginator remembers the doctor as ‘Primary Care Physician’. So, thecall originator has assigned the doctor a nickname called “PCP” andstored it in the caller's TTI account. When viewing the diary on theirTTI account over the Internet, it shows both the actual TTI (i.e.,InternistInPrinceton) and the nickname PCP.

A telephone call receiver may assign their own nickname to a TTI eithervia telephone keypad or via an Internet website interface.

Specific Call Blocking

TTI users can turn on ‘Do Not Disturb’ or ‘Leave Message’ in his/her TTIaccount. They can set these settings for everyone or for a caller with aspecific TTI. When ‘Do Not Disturb’ check box is on the software simplyblocks all or a specific caller, say a rude ex-boyfriend. Similarly,‘Leave Message’ could be turned on when the user is in a meeting anddoes not want to be disturbed. When a TTI of a caller is blocked thenall the TTIs assigned to the their telephone number may be configured tobe blocked.

Caller Specific Ring Tones

Just as the call receiver may block specific callers they can also setdifferent ring tones for different callers and for different TTI dialedby the caller. For example, a doctor-and-lawyer who has two differentTTIs for the same number can set one ring tone for those call him on hisdoctor TTI and a different one for those who call him on the sametelephone using a lawyer TTI. The doctor may set a ring tone for familymembers when they call. So in short, call receiver can set the tonesdepending on both who calls and what TTI they call. If a family membercalls using doctor TTI then the ring tone assigned to the family memberwill ring even though call receiver has assigned a different ring toneto those who call him using the doctor TTI. The present inventionanticipates that these caller-specific ringtones need not always bestrictly a jingle or other prerecorded song, but rather can incorporatevoice announcements such as “Boss is calling” or other vocalizationsthat are generated using a text-to-speech conversion software.

Exemplary User Interface Navigation (0600)-(0800)

As generally illustrated in FIG. 6 (0600)-FIG. 8 (0800), the presentinvention anticipates the following information will be included in manypreferred embodiments:

Basic Information (0600)

After entering the TTI and password the user may be presentedinformation as depicted in FIG. 6 (0600). Within this page subscribersenter the NTI to be assigned to their TTI. This page generally containsthe basic information about the subscriber.

Blocked Names (0700)

This dialog enables the user to enter TTIs from whom they do not wish toreceive a telephone call.

As with other general dialogs depicted herein, row entries may be addedwith the ADD dialog button and removed with the DELETE dialog button.Similar approaches to the Blocked Names dialog may be applied totabs/sections listing of TTIs such as the OGM, Ring Tones, Group, etc.dialogs.

General Dialog Options

The exemplary dialog screen of FIG. 7 (0700) also generally illustratesthat the menu interface may contain a wide variety of options toactivate additional dialogs. Those illustrated include in this exampleinclude:

-   -   Basic Information. This dialog permits the user to define basic        information about the TTI/NTI mapping.    -   Blocked Names. This dialog permits TTIs associated with remote        callers to be call blocked.    -   Group Participation. This dialog allows a given user to        associate other TTI trees within their TTI tree. This permits        merging information from other users in a cooperative social        networking context within a TTI tree and also permits automatic        updating of NTI associations within this context.    -   Call Log. This dialog displays the call log of the user and logs        both incoming and outgoing calls. This optional dialog allows        the user to see all incoming and outgoing TTIs. This data is not        user-modifiable, but does permit the user the option to        associate a NICKNAME (TTN) to the TTI. This permits the user to        select the TTI by TTN the next time a telephone call to this TTI        is initiated. Upon receiving the TTN the TMS will fetch the        corresponding TTI associated with the TTN and use it to fetch        the corresponding NTI.    -   Download. This dialog permits software associated with the        system to be downloaded from the TMS. This optional dialog        allows the user to download the TTI-enabled telephone dialing        software onto their mobile device as generally depicted in FIG.        5 (0500). This dialog is generally for smartphones and the like        where TTI/NTI software is not an integral part of the operating        system.    -   Outgoing Message (OGM). This dialog permits messages sent out by        the user's telephone (or TMS) to be individually defined and        conditioned on events defined by the user.    -   Block Incoming Calls. This dialog permits a variety of incoming        call types to be blocked.    -   Block Outgoing Calls. This dialog permits a variety of outgoing        call types to be blocked.    -   Parental Controls. This dialog permits a parent to define what        calls may be made by the telephone and place limits on telephone        use.    -   Ringtones. This dialog permits unique ringtones to be associated        with individual TTIs, and may include text-to-voice annunciators        for incoming call identification.

One skilled in the art will recognize that this list is not exhaustiveof the options available with the user interface.

Group Participation (0800)

The exemplary dialog depicted in FIG. 8 (0800) illustrates a methodologyby which a STD user may accept requests from TTD users to modify theirTTI trees and incorporate the TTI tree information of third parties.This functionality is described in further detail below.

Group Participation Exemplary Detail (0800)

The Group Participation dialog supports incorporation of TTI trees intoother TTI trees under control of the TTI tree owner. This functionalitymay be generally described in three sections of the exemplary dialogillustrated in FIG. 8 (0800) as described below.

This functionality allows the TTI users to enlist their TTI or linktheir TTI with other TTIs. For example, John Doe having a personal TTIof JDOE may connect with a realtor for ReSel Realtors whose TTI is ReSelhaving a work TTI at ReSel of ReSelBroker1.

The objective of this grouping functionality is to permit showing thepersonal TTI JDOE in ReSel's directory tree and allow ReSel to includeReSelBroker1 in JDOE's personal directory tree.

Reauest Sent Section (0810)

This Request Sent section (0810) shows list of TTIs to whom the STD havesent requests/authorizations to include a TTI in their TTI directorytree.

For example, at work place, a person may show their personal TTI alongwith their work telephone number. For example, John Doe may desire toshow their personal TTI JDOE along with their work TTI ReSelBroker1.ReSel Realtors cannot just list the TTI JDOE in their TTI directory.They will need John Doe's request/authorization. So, in the Request Sentsection (0810) of John Doe's TTI profile, John Doe will enterReSelBroker1, signifying that JDOE is requesting to be listed withReSelBroker1. John Doe can add a list of all TTIs in this dialog whomthey have sent the request or authorized to list their TTI (e.g.,cubscoutsoflL, golfloversofmiami, etc.) or they may selectively add ordelete them (see ‘Add’ or ‘Delete’ options available in this dialog).

At this time, when ReSelBroker1 is ‘Added’ via this dialog, this is onlya request/authorization. This does not mean that JDOE will automaticallyappear along with ReSelBroker1 in ReSel's directory tree. For that tooccur ReSel Realtors can either accept (i.e. include) or reject(exclude) the request/authorization as detailed in the Request Receivedsection (0820).

However, if John Doe deletes a TTI ReSelBroker1 from the Request Sentsection (0810), then the ReSelBroker1 will be removed from the RequestSent section (0810), and John Doe's TTI JDOE will not be in ReSelRealtors “Received Requests/Authorizations” (Request Received section(0820)) and it will also not appear in the directory tree ofReSelBroker1.

Referencing FIG. 8 (0800) and the top portion of the dialog (0810), whena TTI ReSelBroker1 is entered here program on TMS sends a request onbehalf of JDOE to

ReSelBroker1 and puts the TTI JDOE in ReSelBroker1's Request Receivedsection (0820). The software on the TMS will then populate the RequestReceived section (0820) of these people with the TTI JDOE and all theTTIs listed here will see JDOE appear in the Request Received section(0820) of their corresponding profile. It should be noted ReSelBroker1itself will appear under the TTI ReSel, creating a hierarchy of TTIs.

If the DELETE option is selected here the TMS deletes TTI ReSelBroker1from JDOE's “Request Sent” list.

Software on TMS deletes TTI JDOE from the Request Received section(0820) or the Directory Tree section (0830) of ReSelBroker1 (i.e. TMSsoftware removes JDOE from Requests Received section (0820), if JDOE'srequest was not accepted by ReSelBroker1 and Directory Tree section(0830), if ReSelBroker1 had already accepted JDOE's request).

The exemplary dialog includes an ADD option or an empty “Request Sent”box to allow JDOE to enter new TTIs for adding additional TTIs to thislist.

RequestReceivedSection (0820)

The Request Received section (0820) shows a list of TTIs of other peoplefrom whom the STD has received request/authorization to include theirTTI in the current TTI directory tree.

Just as John Doe requested ReSel Realtor to show their personal TTI inthe Request Sent section (0810), ReSel Realtors may also want John Doeto show their work TTI ReSelBroker1 along with along with their personalTTI JDOE. So, just as John Doe had sent them a request/authorization,now they have sent John Doe a request/authorization to show work the TTIReSelBroker1 along with John Doe's personal TTI. So now, in the RequestReceived section (0820) ReSelBroker1 appears, waiting to be accepted sothat ReSelBroker1 will appear along/under the personal TTI JDOE. Justbecause someone sends a request does not mean that the receiver of therequest must associate their personal TTI along with their TTI. Useroptions are provided to include or exclude each name in this waitinglist. When the user selects INCLUDE, ReSelBroker1 will show in the TTIdirectory (Directory Tree section (0830)) and if the user selectsEXCLUDE ReSelBroker1 will be deleted from the Received Request section(0820) and will not be shown in John Doe's TTI directory.

Referencing FIG. 8 (0800) and the Received Request Section (0820), theTTIs of other people on this section may be received by JDOE. JDOEcannot enter TTIs of other people in this section. So unlike Section(0810) there is no “Add” button in this section. TMS software populatesthis section when someone enters JDOE's name in their “SENT TO” section(0810).

By selecting the INCLUDE option of this section, JDOE can choose to addthese names to his own directory tree. If JDOE selects INCLUDE, then TMSsoftware removes the name from this section and populates it in theDIRECTORY TREE Section (0830).

By selecting EXCLUDE options of this section, JDOE can choose to denythe request of the sender. TMS software removes the TTIs from theReceived Request section (0820) “without” populating it in the DirectoryTree section (0830) of JDOE's profile.

Directory Tree Section (0830)

This dialog area shows all the TTIs that have been accepted by theINCLUDE option in the Received Request section (0820). These TTIs willbe currently shown in the TTI directory tree section (0830). Thisfunctionality will only allow the user to delete a TTI but not directlyadd to it. All the additions to this section will come through theReceived Request section (0820) as explained above.

The Directory Tree section (0830) may also allow the subscriber toprioritize/arrange and delete the hierarchy of all the TTIs in atree/org chart format. This section's functionality is similar to atypical file directory tree structure as depicted in a graphical userinterface (GUI) such as MICROSOFT® WINDOWS EXPLORER file directorystructure. TTIs listed in section (0830) generally depict what isavailable for the CO to dial under the TTI JDOE in this example.

Some of the TTIs appearing in this section (0830) may show up in thedirectory tree form when the CO enters a TTI. This will give the COoptions to scroll thru all the TTIs available for him to reach a givenCR. However some of TTIs appearing in the hierarchy of this section(0830) will NOT show up in the CO STD. These TTIs may be hidden. Inorder to reach someone thru those hidden TTIs, the CO may be required toinput the entire TTI path (e.g., jdoe/jdvacationhome). This display andhidden feature of directory is necessary for big corporations, wherethey want the public to be able to scroll thru the menu of availableoperators and receptionists but in order to reach a specificmanager/executive the caller will have to be specific as to who theywant to reach. For example ReSel/ReSelceo where ReSel is the TTI ofReSel Realtor and ReSelceo is TTI for the CEO. ReSel may not want topublicize the CEO's TTI to everyone. The TTI ReSelceo does not appear onthe STD for the ReSel directory tree, but it is still available to theCO.

Just like John Doe, ReSel Realtors may process therequests/authorizations of TTIs received from and sent to differentpeople/businesses. This Grouping of TTI functionality allows a verycomplex, extremely powerful, and global networking of people, interestgroups, and business all over the world, where not just the employee'swithin a company but also larger groups of people may choose to build adirectory tree of their interest groups.

Referencing FIG. 8 (0800) in the Directory Tree section (0830), thissection shows all the TTIs which will appear on the CO's screen whenthey dial JDOE. If JDOE is the only entry here and there are no TTIentries or sub entries here then STD will directly proceed to get NTIand further proceed to initiate the call. However, if there are moreTTIs listed here in addition to JDOE (as shown in the Directory Treesection (0830)) then STD will display the directory tree and wait for COto make selection. Only those TTIs from this section will be shown whichhave been enabled by the SHOW option.

Just as in the Received Request section (0820) John Doe cannot add TTIshere. These additions must come thru the Received Request Section(0820).

TMS will always populate at least one TTI as a root TTI in this section(i.e. the TTI of the TTI subscriber himself such as JDOE in thisexample).

Software on TMS or a Web browser may allow the user to manipulate andreorganize the hierarchy in this section in a manner similar tore-organizing a directory tree in a MICROSOFT® WINDOWS® FILE SYSTEM.

The Directory Tree example shown in (0830) depicts a minimal profile andmay be expanded for large organizations and corporations.

Exemplary Calling User Interface (0900)

While the present invention may incorporate a wide variety of callinterfaces, an exemplary embodiment is generally illustrated in FIG. 9(0900) wherein the caller (“Jane Doe”) selects from one of severaloptions to call the secretary of “John Doe”. Note that thisconfiguration permits a number of dropdown lists (0911) to be associatedwith the target call receiver and that these lists may be dynamicallyupdated based on the availability of the call recipient and/or theirtelephone.

In addition to the TTI tag that may be associated with one or more NTIs,the present invention anticipates that graphical icons (including butnot limited to photographs, company logos, and other graphical indicia)may be used to identify the TTI graphically. Thus, the tree structure inFIG. 9 (0900) may optionally include a graphical “hot spot” forselection of a given TTI entry. In some preferred invention embodimentsthe TTI tree may be entirely described using graphical entries with theTTI textual description embedded within the graphical icon definition.This TTI graphical information may be maintained within the TMD and/orthe STD/TTD infrastructure.

Furthermore, it should be noted that any of the TTIs depicted maycomprise just a NTI in some circumstances.

As generally indicated in FIG. 9 (0900), scroll bars may be implementedwithin any of the dialogs described herein to provide a means ofnavigating displayed data structures that are larger than the screendisplay area.

Exemplary Recipient Autorouting (1000)-(1100)

As will be detailed elsewhere herein, the present invention mayincorporate conditional prioritization of TTI/NTI pairings associatedwith a TTI. For example, a TTI might reference “John Doe” but refer to alist of potential NTIs at which “John Doe” may be reached. This list maybe rearranged or modified/augmented/reduced based on a string ofconditional events known to or provided to the TMS. For example, thecontact for “John Doe” may require communication at the OFFICE DESKduring morning hours (as generally illustrated in FIG. 10 (1000)) butduring the afternoon any calls should be routed to the FIELD office asgenerally depicted in FIG. 11 (1100). Note that in either of thesecircumstances the information below the main “John Doe” entry may beoptionally hidden from view so that the call selection and routingoccurs automatically and with no additional input or selection by theoriginating caller. This feature has significant benefits in reachingpersonnel who are highly mobile and have a variety of communicationmethods available to them.

Exemplary “Call as” User Interface (1200)

A person who has chosen multiple TTIs for just one STD telephone numbercan also choose which TTI to use while calling someone. For example, aperson who is both a doctor and a lawyer who has two different TTIs forthe same number can call one client using a doctor's TTI and anotherperson using a lawyer's TTI from the same telephone. This interface isgenerally illustrated in FIG. 12 (1200) wherein the example providedindicates a call from “Jane Doe” to the field office of “John Smith” anddoes so with the calling persona of “Jane Doe” being associated with herbusiness function at “FooBar, Inc.” Note that this “masking” of STDpersona makes it possible for a caller to not only present differenttelephone personas based on transmitted TTIs to the receiving TTD, italso permits persons who work at home to present a professional personawhen communicating with business clients. This feature eliminates theneed for a single person to carry multiple phones for multiple purposes.With this feature enabled there is no need for a person to carryseparate phones for work and personal use.

The present invention anticipates that this feature may permit theidentification of the calling persona to have multiple identificationfields. These fields may include but are not limited to the following:

-   -   A local persona name that is displayed on the STD menu        (“Business”/“Office”);    -   A remote persona name that is displayed on the TTD when the call        is received remotely (“Baby Sitter” or “FooBar, Inc.”; and    -   A remote persona name that is defined based on classifications        of targeted TTDs (as for example specifying a more formal        presentation for some business clients or not displaying        photograph icons for some clients.        One skilled in the art will recognize that other modifiers to        the basic TTI data structure are possible and thus the structure        depicted in FIG. 12 (1200) is only exemplary of many        possibilities.

Person-Specific Outgoing Message (OGM)

When the telephone line is busy or when call is not picked up thencurrent telephone setups and answering machines allow only one OutgoingMessage (OGM) as a generic message to the caller when the telephone isunanswered or as in the case of telephone setups in the corporations itallows the person a second OGM when the he/she is on the telephone (“Iam currently on the telephone”). However, TTI users can setup multipleOGM on the TTI account on the web page, each of which can be playedspecifically when a person with a predetermined TTI calls. For example,a TTI user may setup a first OGM when their husband calls, a second OGMfor the son, a third OGM when the boss calls and wants to leave amessage, and a fourth OGM for the general public.

Incoming Messages

Incoming messages may be optionally forwarded to email address set onthe TTI account as a voice file.

Internet Based Personal Telephone Diary

The TMS website maintains a log of STD/STI and TTI calls automatically.Thus, the next time when a user changes telephone equipment they simplydownload all or some of the frequently used ‘TTIs’ from their TTIaccounts. TTI users may also upload current dialing diary from theirtelephones to their TTI account on the TMS.

User Controlled Call Logs

Software on the TMS or telephone exchange may keep a log of telephonecalls. Telephone companies may provide the log of calls along with thetelephone invoice. But they give only one log for one telephone number.However, the present invention teaches this control is also in the handsof the TTI users and not the telephone company. Since the public will beable to structure multiple TTIs for one telephone number based on theirpersonal needs, they will also be able to see the separated call logsunder each TTI, even though these TTIs belong to the same telephonenumber.

International TTIs

TTI software may warn the caller if it is about to dial internationalnumber. A caller who frequently makes such telephone calls candeactivate the warning.

Enhanced Voice Menu Functionalities Using TTIs

Under current telephone voice menu systems one company voice menu maysay “dial 1 for Accounting Department, 2 for Sales” while other companytelephone voice menu may state “dial 1 for Sales and 2 for Accounting”.Using the TTI/NTI mapping as taught by the present invention, theoriginating caller dials only the company's TTI without adding aspecific department or a person's name, then in additional to voicemenus they will be presented the list of departments or employees TTIson the telephone screen. Instead of waiting for lengthy, annoying, andcomplicate voice menus currently in use, the telephone interfacesoftware installed on these STDs allows the caller to search, scroll, orhighlight the appropriate department, business unit, employee, etc.,then make a selection and initiate the telephone call.

The same list of TTIs may be accessed by the public via computers, andviewed it in a tree format (just as file directories are shown inWindows Explorer). Businesses often have whole list of complexdepartments in various locations each having multiple operators. Callingthese companies to reach a particular department or an operator is oftena very frustrating experience. Callers have to patiently listen tocomplex menus, make appropriate selections only to find that the personor the department they are trying to reach is either closed/unavailableor it is not the correct department. The use of graphical displays ofTTIs in a hierarchical structure within the present invention eliminatesthis menu complexity and promotes a rapid access method to thecommunication infrastructure within a company.

Business/Individual Telephone Directory Tree

Individuals and corporations with TTIs will be able to Sub Assign theirwork TTIs, Fax Names, etc. to their main TTI in Group Participation. Inturn they can “Sub Assign” their individual TTIs to their employers TTITree. Individuals can list their work TTI under their personal TTI andvice-versa.

Availability Status

The availability status of the people in the department is also shown ifthey have interfaced their TTI account with the scheduling programs suchas MICROSOFT® OUTLOOK® or Lotus Notes. The availability status arefurther categorized and shown as currently busy on the telephone, out ofoffice, in meeting, do not disturb, out for lunch, be back in 10 minutesor all the blocked time in the outlook can be shown as “unavailable”.

When these corporate TTI trees are interfaced with the schedulingsoftware such as MICROSOFT® OUTLOOK® or LOTUS NOTES® then along with theTTIs caller can also see who is in the office, which TTI is busy, who isin meeting and who has do not disturb flag turned on next to their TTI.This will come handy when someone is trying to call a business wheremost of the operators are very busy. Instead of constantly listening toannoying message “All operators are currently busy”, just by giving aglance on the screen a caller can see if most of the operators are busyand what would be the wait time.

Free Operator Selection

Callers directly select the party/operator they are trying to reach; theone who is neither on the telephone or away for lunch, or not in theoffice. By selecting the party caller's telephone can directly dial theappropriate “TTI” or “Cyber Name”.

Attach Company/Individual Logo to the TTI

Along with the TTI, individuals and corporations can store theirpictures, logo, drawings, short movie clip, GPS location, GPS locationtranslation, a message etc., on their TTI account. This logo, pictureare displayed on the callers screen when they call receivers TTI isdialed by the software. Logos are also displayed when anyone searchesfor the company's TTI over the Internet.

Global Telephone Directory

As more and more companies and businesses register for the TTIs via theTMS they automatically become part of a global telephone directory,which can be searched by the public on-line.

Reserved TTIs

TTIs such as “Police”, “Hospital”, “Emergency”, may be reserved in somepreferred embodiments. When a person dials these numbers then dependingupon the local area code the nearest telephone number may be accessed bythe system. Department or branches within the police, hospitals, etc.may be sub-assigned to the Police, hospital, TTIs, etc.

REMOTELY INITIATING A TELEPHONE CALL Example 1

When a person is looking for used auto part in local junk yards. He logsinto his TTI account on a computer. He browses the TTI website for junkyards in the area.

He selects each junk yard on the list and requests a call trigger forselected junk yard. At this time, the TTI web-site sends the TTI of theselected junk yard to his cellphone via SMS, text messaging or similartechnology. Upon receiving this message from the web-site, the TTIsoftware on the telephone equipment recognizes it as a legitimate TTIand initiates the telephone call. In this situation, after looking upthe TTI on the web-site (either through a computer or through her mobiletelephone) the person does not have to punch in the TTI of each junkyard he is trying to reach.

Example 2

Similarly, when Mr. A is searching for TTI of Panasonic's repairdepartment on TTI website. When he finds the department and a specificindividual from the telephone list then he need not go to his telephoneand punch in the TTI to initiate the call. Instead, upon selecting theTTI on the computer when he clicks the call initiate icon next to it,the TTI web-site sends the telephone number directly to his cellphonevia SMS. This will come very handy when someone is shopping andcomparing rates.

Non-Internet Users

Those who are not Internet/web savvy can continue to use telephonenumber instead of name. However, telephone companies can ask them whatname they would prefer for their number and open a TTI account for themfor use just in case. At present, the telephone companies assign all thetelephone owners a telephone number. Similarly, the telephone companiescan assign TTIs too.

Synching Calendars

When a TTI subscriber chooses to sync up his MICROSOFT® OUTLOOK®calendar with TTI then he will need to download a software on hiscomputer which will read his calendar event and update the his profileon TTI website. Thus, when another Call Originator (CO) enters a CallReceiver (CR) TTI then the TTI software on CO's name will connect to theTTI website and pull out CR's profile as well as the calendar event. IfCR is in a meeting then even before dialing the number the TTI softwareon caller's telephone will display that CR is in a meeting and whetherto proceed with the call or not.

Parental Control/Warning/Call Restriction

A TTI subscriber's TMD profile may also have features such as parentalcontrol where parents will be notified for certain restricted numbers.or caller will be allowed to call only those TTIs and telephone numberswhich parents have listed in the subscriber's TTI profile.

Child/Parent Identification Feature

When a children are given a TTI profile then this name could be usedthroughout their life, permanently. Therefore, in case of lost childrenthey can always contact family anytime. Also when the profile is givento law enforcement they can keep permanent tracking on the use of theTTI.

Emergency TTI Feature

Certain TTIs will be ‘permanently blocked’ & for ‘internal use only’ andpublic will not be able to subscribe to them. However they can certainlyuse them. E.g. Police, Hospital, Fire. All the language translations ofthe word of these words TTIs will be blocked; e.g. TTI for ‘Police’ inEnglish; ‘Polizia’ in Italian; ‘policie’ in Czech will all bepermanently reserved for ‘Internal Use Only’.

There will be special method for these TTIs (i.e., when someone dials aone of these TTIs, the software on the server will send to the caller'ssmartphone, the multiple telephone numbers of nearest Police Departmentbased on the GPS location of the caller). In these cases system will notcompare the caller's own telephone number, area code, country code toform a complete telephone number to dial. Instead the complete telephonenumber will be computed based on the GPS location. Also these telephonenumbers will be ‘Displayed’ and need not be hidden on the caller'stelephone. So that for some reason if the caller wants to these numbersdirectly via another ‘Non Smart Telephones’ then they can do so.

TTI Case Sensitivity

All TTIs may be configured to be case insensitive. E.g., ‘Jim’, ‘JIM’and ‘jim’ may be considered one and the same TTI.

TMS Call Initiation

The present invention anticipates that the TMS may initiatecommunication between two or more cooperating parties by sendingmessages to TIDs associated with a plurality of STDs and/or TTDs. Inthis manner it is possible to generate conference calls between aplurality of parties under direction of the TMS. This TMS callinitiation system may incorporate interfaces to MICROSOFT® OUTLOOK® orother calendaring software to determine when to initiate these calls.

This feature may be integrated with desktop/laptop/tablet computingdevices to permit video or other data to be displayed during thetelephone conversation. In some circumstances the computer network willhave insufficient bandwidth to support full streaming video/chat butwill have sufficient bandwidth to support auxiliary data traffic to thedisplay to augment a telephone call using a cellular telephone or othermobile communication device.

TTI Tree Navigation

The present invention anticipates that a TTI may comprise one or more“paths” that operate similar to a traditional directory tree structurefound in many file systems. This tree structure may be navigated usingconventional UP (BACK) and DOWN (EXPLORE) tree navigationkeystrokes/mouse clicks within a variety of GUI displays that are wellknown in the art.

TTI Graphical Icons

The present invention anticipates that a given TTI may have associatedwith it a “shortcut” graphical icon that may be displayed on the STD/TTDduring call initiation/execution/completion. In this manner, the TMD mayserve as a repository of validated icon information associated with agiven STD of known characteristics.

For example, current telephone caller ID features can be “spoofed” usingtechnology that sends false caller ID information to the recipient of atelephone call. By acting as a trusted third party intermediary, the TMScan generate trusted icons and/or other graphical information (such astrusted photos, company logos, receiver-defined graphics, etc.) that areonly known to the TMS within the TMD and not generally available to thepublic. This information can be used to define the user interface on theTTD and thus permit the TTD user to verify the identity of the STDcaller.

Call Blocking System (1300) Call Blocking Overview

The present invention anticipates alternate system embodiments thatincorporate a methodology for telephone call recipients to rejectunwanted calls by logging the call as a “blocked” call within theTTI/NTI mapping database (TMD). While this call blocking functionalitymay have many applications, it can effectively be utilized to eliminate“robocalls” (automated sales/marketing calls that are generallyprohibited by government agencies such as the Federal Trade Commission(FTC).

The Federal Trade Commission (FTC) has challenged innovators to createsolutions that will block illegal robocalls. The solutions sought by theFTC should block robocalls on landlines and mobile phones and mayoperate on a proprietary or non-proprietary device or platform. The vastmajority of telephone calls that deliver a prerecorded message trying tosell something to the recipient are illegal. As technology has advancedover the years, so have the number of illegal robocalls.

Telephone companies typically have no incentive for blocking therobocalls. This is especially true on cellphones as more calls mean moreairtime and more revenue for the telephone company. Thus, telephonecompanies have been slow to implement technology that blocks robocalls.

Exemplary Call Blocking System

An exemplary call blocking system is generally illustrated in FIG. 13(1300), wherein the system is substantially similar to that of FIG. 1(0100) with the exception that the TMD (1313) is augmented with aTTI/NTI call blocking list (1314) listing TTIs that are call blocked bythe TTD (1330) (or by government or other similar legally mandated NTI(e.g. Fraudsters, etc.)) via control messages (1332) sent to the TMS(1311). The embedded TMS (1311) software (1312) incorporates anadditional TTI call blocking screening process (1315) that attempts tomatch a TTI translation request (1322) from the STD (1320) with the callblocked list (1314) provided (1332) by the TTD (1330). If a match is notdetected, the resolved NTI is sent (1323) is sent to the STD (1320).Otherwise, if the TTI is matched to the call blocked list (1314), theTTI is not translated and the call is not completed. Within this contextthe STD (1320) return message (1323) may incorporate an error messageand the TTD (1330) may be notified (1333) of the blocked call. In somecircumstances the STD (1320) may not be notified of the rejected callbut rather the call may just fail to be processed or initiated to theTTD (1330).

Variants of this system configuration may also use a variety of otherkeys to activate the call blocking feature, including but not limited tothe following:

-   -   The resolved NTI of the TTI.    -   The machine CPU ID of the STD.    -   SIM card serial number of the STD. A subscriber identity module        or subscriber identification module (SIM) is an integrated        circuit that securely stores the international mobile subscriber        identity (IMSI) and the related key used to identify and        authenticate subscribers on mobile telephony devices (such as        mobile phones and computers).    -   URL/IP address of the STD.    -   IP address of the STD.        Thus, the present invention anticipates that any key that may be        used to identify the STD (1320) may be used as the basis (1314)        for the call blocking screening process (1315).

As indicated in FIG. 3 (0300), an alternative system implementation ofFIG. 1 (0100) may be implemented with the TMS being integrated withinthe PSTN. The present invention also anticipates that the call blockingsystem depicted in FIG. 13 (1300) can be implemented within the contextof the PSTN as a parallel to the system configuration depicted in FIG. 3(0300). The details of this implementation are identical to thatpresented in FIG. 13 (1300) with the exception of the placement of theTMS as being PSTN-integrated.

Call Blocking Method (1400)

A method associated with the system depicted in FIG. 13 (1300) isgenerally illustrated by the flowchart in FIG. 14 (1400) and comprisesthe following steps:

-   -   (1) The Call Originator (CO) enters the target telephone        identifier (TTI) for the Call Receiver (CR) on a source        telephone (telephone instrument device (TID)) (STD) (1401).    -   (2) The STD sends the TTI along with other relevant details such        as the caller's TTI and password to the telephone mapping server        (TMS) (1402).    -   (3) The TMS searches for the TTI within the TMD and retrieves        TMD data associated with the TTI (1403).    -   (4) The TMS determines if the associated TMD data is call        blocked from access by the STD, and if not, proceeds to step (6)        (1404).    -   (5) The TMS rejects the TTI mapping request and issues an error        message to the STD and proceeds to step (9) (1405).    -   (6) The TMS sends back the numeric telephone identifier (NTI)        (telephone number) to the STD (1406).    -   (7) STD dials the NTI to connect the CO STD and the target TID        (TTD) associated with the CR (1407).    -   (8) The telephone call is routed through the public switched        telephone network (PSTN) through the telephone company central        office (CCO) to the TTD associated with the CR (1408).    -   (9) The method is terminated (1409).

Within this context a variety of optional activities are anticipated,and may include informing the STD and/or TTD of the blocked call. Notethat blocked calls can be used in some circumstances to block callswhile the TTD is determined to be scheduled for a meeting or otherblocked activity (present in a movie theater as determined by GPS, etc.)

Exemplary TTI Definition System/Method (1500)-(1600) Exemplary TTIDefinition System (1500)

While the present invention anticipates that many methodologies may beemployed to permit a user to create a TTI/NTI mapping entry within theTMD, an exemplary system configuration to accomplish this is generallydepicted in FIG. 15 (1500). Here the system operates using a web-baseddata entry application (1501) (generally executed on a computing devicerunning software read from a computer readable medium) that interfaceswith a user interface (GUI) (1502) (generally a web browser or otherGUI). This GUI (1502) may be augmented by data extraction applications(1503) that operate on user data (1504) to extract TTI/NTI informationfor processing by the web application (1501) for storage in the TMD(1513).

The user generally interacts with the GUI (1502) to define variousTTI/NTI associations and associated parameters and conditionals, editingthis information (1505) within this context as necessary. This resultsin an internal data structure representing TTI branch definition data(1506). Once this process is completed, the TTI branch definition data(1506) is processed by a TTI validation process (1507) that is furtherdetailed in FIG. 16 (1600). If the validation process (1507) indicatesan approved TTI (1508), the TTI/NTI branch definition data (1506) isthen stored (1509) in the TMD (1513). An approval failure is generallyfollowed by additional user edits (1505) within the web application(1501).

Note that the system as illustrated may permit TTI definitions for NTIsnot associated with telephones that are Internet-enabled. For example,it is possible using this system to define TTIs for conventional“landline” telephone, PBXs, etc. that are not capable of communicatingwith the TMS/TMD as described herein.

Exemplary TTI Definition Method (1600)

An exemplary TTI validation process associated with this system isgenerally illustrated in FIG. 16 (1600) wherein the method generallyincludes the following steps:

-   -   (1) Process the proposed TTI with a multi-lingual dictionary        parser to extract token trees from the TTI string and place them        in a local TTI token data structure (1621) for further        evaluation (this breaks up the TTI into portions that may have        meaning in a variety of languages) (1601);    -   (2) Match the TTI tokens (1621) against a number of dictionaries        (that may be multi-lingual) (1622, 1623) to produce a set of        comparison match results (1624) that will be used to determine        TTI validity (1602);    -   (3) If the TTI match (1624) indicates that the TTI may include a        trademark, perform a trademark approval process (1625) to ensure        the user has authorization to use the trademark (1603);    -   (4) If the TTI match (1624) indicates that the TTI is reserved        word, proceed to step (10) (1604);    -   (5) If the TTI match (1624) indicates that the TTI is an        improper (foul/vulgar) word, proceed to step (10) (1605);    -   (6) If the TTI match (1624) indicates that the TTI is already in        use by another user, proceed to step (10) (1606);    -   (7) If payment is not required to register the TTI, proceed to        step (9) (1607);    -   (8) Process a user payment for registration of the TTI (1608);    -   (9) Flagging the TTI as APPROVED and proceeding to step (11)        (1609);    -   (10) Flagging the TTI as REJECTED (1610); and    -   (11) Terminating the validation method (1611).

Here it can be seen that the TMS serves as an authentication gateway toensure that TTI identifiers satisfy a host of constraints to make themunique, reliable, and secure. One skilled in the art will recognize thatthe list of validity checks detailed in FIG. 16 (1600) is only exemplaryof other types of validation that may occur during the TTI registrationprocess.

TTI Hierarchical Path Structure (1700)-(1800)

The TTI may incorporate a hierarchical path structure as detailed inFIG. 17 (1700). Within this context, a specified TTI mapping mayincorporate a tree structure and be specified to incorporate any pathalong that tree structure. As detailed in FIG. 17 (1700), the path“Alpha\Beta\ . . . \Gamma\Delta” would point to the resulting NTIincorporating the telephone numbers “{555-555-1111, . . . ,555-555-9999}.” The present invention teaches that partial pathsincluding only a portion of the full path may be used to specify theresulting NTI. For example, use of “Delta” as the partial path wouldresolve to the first tree element matching that term, or the full path“Alpha\Beta\ . . . \Gamma\Delta”. Similarly, specification of “Beta”would result in “Alpha\Beta” with the path being truncated at that pointindicating no terminal NTI elements but resolving to include theremaining tree elements “ . . . \Gamma\Delta” as potential paths tofollow.

This hierarchy may be used to define geographical or other relationshipsbetween various TTI atomic path elements. For example, as generallyillustrated in FIG. 18 (1800), a geographic TTI path could be definedfor “John Doe” located in “Dallas, Tex.” to be“World\NorthAmerica\U.S.\Texas\Dallas\JohnDoe” which would resolve totwo potential TTI paths including “Work” (555-555-1111) and “Home”(555-555-9999). This type of hierarchy can permit localization ofindividuals/businesses/etc. to a particular geographic region.

Local TTI Tree Branch Control (1900)

The present invention anticipates that the TTI trees depicted in FIG. 17(1700)-FIG. 18 (1800) may incorporate branches that are controlled andmanaged independently of the main TTI tree. As generally depicted inFIG. 19 (1900), a TTI branch head (1910) at any level can reference oneor more branch trees (1920, 1930) that may be independently maintainedand controlled by separate entities such as companies or individuals.Thus, changes within the individual TTI branches (1920, 1930) can bemaintained by the individual owners of the branches and automaticallyupdated within the overall TTI root NTI lookup structure.

TTI Search Path (2000)

Within any application interfacing with the TMS there is anticipated tobe a mechanism for defining set of “search paths” associated with listof TTI trees from which a user may set their localized “environment” forTTI searching. For example, as illustrated in FIG. 20 (2000), a searchpath might be of the form “US\Texas\Dallas; US\Texas\Houston;US\Texas\NorthTexas;” which would search these individual search pathsto find the TTIs matching data entered in to a user dialog box. Thissearch path methodology may incorporate a wide variety of other types ofTTI groupings. For example, it is possible to define a search pathincluding the terms “LinkedIn\NewsGroup” or “Facebook\Friends” toincorporate potential telephone number information associated with aLINKEDIN® “NewsGroup” group or to scour for information on your“friends” within FACEBOOK®.

TTI Access Control Lists (ACLs) (2100)-(2200)

The present invention may in some preferred embodiments implement theuse of Access Control Lists

(ACLS) that permit modification of TTI entries to incorporate TTI linksprovided by parties other than the owner of the TTI hierarchy. In thisfashion, a TTI hierarchy can be managed by a TTI owner, but the TTIowner may permit insertion of TTI information not managed by the TTIowner within the TTI hierarchy.

An example of this is generally illustrated in FIG. 21 (2100), whereinthe OFFICE TTI link (and its associated hierarchy) is managed andcontrolled by ACME Company and not JOHN DOE, the owner of the TTI tree.The ability to modify the OFFICE link may be in many forms, but manypreferred forms may use an Access Control List (ACL) as indicated thatassociates a username/password chain with a given TTI chain element asgenerally illustrated in FIG. 22 (2200). Each username/passwordcombination may be associated with an authorized access mode (forexample: R—read TTI; W—write TTI; E—call TTI; D—delete TTI). One skilledin the art will recognize that other forms of authorization access maybe incorporated in this generalized ACL structure.

Outgoing Call Blocking (2300)

As generally depicted in FIG. 23 (2300), the present inventionanticipates that in some preferred embodiments the STD (2320) may define(2326) (under password control) an outgoing call blocked list (2315)that may be integrated in the STD (2320) and/or the TMD (2313). Thiscall blocked list (2315) permits outgoing calls to be screened such thatthe outgoing TTI call request (2322) is first screened by the blockedcall list (2315) before being matched (2325) against the TTI/NTImappings (2314) within the TMD (2313). This feature permits parental (orother) controls for outgoing calls to limit the scope of calls that maybe placed from the STD (2320), and may incorporate country/area/exchangeblocking and a variety of phone number masking techniques to limit thescope of calls that may be placed from the STD (2320).

It should be noted that while the system depicted in FIG. 23 (2300)implements forward calling, the system configuration may incorporateforward and/or reverse calling methodologies as taught herein with orwithout the use of call queueing as taught herein.

Incoming Call Blocking/Prioritization (2400)

As generally depicted in FIG. 24 (2400), the present inventionanticipates that in some preferred embodiments the TTD (2430) may define(2436) (under password control) an incoming call blocked list (2415)that may be integrated in the TTD (2430) and/or the TMD (2413). Thiscall blocked list (2415) permits incoming calls to the TTD (2430) to bescreened such that the incoming TTI call request (2422) is firstscreened by the blocked call list (2415) before being matched (2435)against the TTI/NTI mappings (2414) within the TMD (2413). This featurepermits parental (or other) controls for incoming calls to limit thescope of calls that may be received by the TTD (2430), and mayincorporate country/area/exchange blocking and a variety of phone numbermasking techniques to limit the scope of calls that may be received bythe TTD (2430).

In addition to call screening/blocking, the incoming call blocked list(2415) may incorporate a call PRIORITY associated with a given TTI (orTTI chain) such that as the call is received by the TTD (2430), it isautomatically prioritized in the TTD call queue based on a queuepriority as defined by the TTD within the call blocked list (2415).Thus, the TTD (2430) may prioritize incoming calls from a given STD TTIbased on a fixed priority level or a priority level that varies based ona calculated value such as calendar events and other criterion. In somecircumstances the priority level may be set to a value that completelyblocks the incoming call, as for example a parent who wishes to callblock all calls for their daughter after 10 pm at night during schooldays, etc.

It should be noted that while the system depicted in FIG. 24 (2400)implements forward calling, the system configuration may incorporateforward and/or reverse calling methodologies as taught herein with orwithout the use of call queueing as taught herein.

TTI Integration with Web Services (2500)-(3200) TTI/NTI Mapping Metadata(2500)

The TTI/NTI mappings may be directly populated within a TTI/NTI MappingDatabase (TMD) (0113) as generally illustrated in FIG. 1 (0100) or insome preferred embodiments as generally illustrated in FIG. 25 (2500)this database (2513) may be populated automatically by using a webcrawler subsystem (2510) to scan web pages maintained within anenterprise computing environment (2520). Within this context the TTI/NTIMapping Server (TMS) (2511) has augmented software functionality tooperate as a web crawler (2512) to “scan” the Internet (2501) for webpages that contain metadata incorporating TTI/NTI mappings. As thisinformation is scanned from the web over the Internet (2501) and placedin the TTI/NTI Mapping Database (2513). One skilled in the art willrecognize that a dedicated web crawler server could be used in thisscenario and that the TTI/NTI Mapping Server (TMS) (2511) could beoperated as a separate computer in this configuration.

In this scenario, the enterprise environment (2520) maintains a webserver (2521) running web hosting software (2522) that services a webpage database (2523) (that could be as simple as a directory of HTML webpages (2524) supported by the server (2521)). Within these web pages(2524) metadata (2525) is stored which may or may not be visuallydepicted on the displayed web page. This metadata (2525) can incorporateTTI/NTI mapping strings (2526) that may be directly populated in theTTI/NTI Mapping Database (TMD) (2512) once detected in the metadata(2525). These TTI/NTI mapping strings (2526) may be configured todirectly represent a hierarchical organizational directory structure(2527) within the enterprise (2520). In some circumstances theorganizational directory structure (2527) may be represented by internaldocuments such as MICROSOFT® WORD® documents and/or MICROSOFT® EXCEL®spreadsheets (2528) (or any other query of a database or data fileformat such as a sequential file incorporating insert/update/delete ofTMD using SQL or any programming language such as C, Visual Basic, Java,etc.). Traditional database update methodologies may also be used, suchas direct software interfaces using SQL (Standard Query Language).

Exemplary TTI/NTI Mapping Metadata Structure (2600)

An exemplary TTI/NTI directory mapping structure is generallyillustrated in FIG. 26 (2600) and comprises a TTI tree (2610) withconstituent TTI branches (2620), subbranches (2630) (a given TTI tree(2610) may have nested branches and subbranches to any depth), andterminal NTI values (2690). This diagram (2600) generally illustratesthe fact that hierarchical TTI structures taught by the presentinvention are general tree structures and may be nested to any depth.Also illustrated is the use of NTI sequence modifiers (“x NNN” toindicate selection of an extension once the main number has been dialed;“/” to indicate selection of DTMF keypad navigation options; “@” toindicate availability via e-mail; and “www” to indicate indirection toanother web page incorporating TTI/NTI metadata).

Exemplary TTI/NTI UI Navigation Structure (2700)

The TTI/NTI Mapping Metadata Structure depicted in FIG. 26 (2600) mayresult in a search results screen as generally illustrated in FIG. 27(2700). Note that the telephone numbers have been hidden in this dialog,as they are maintained by the TTI/NTI database. Options to return to aprevious directory level (BACK) (or scroll up/down or sideways in amanner similar to a WINDOWS® file directory), change a current directoryentry (EDIT), and provide more details on the directory entry content(DETAILS) are also provided in this exemplary user interface.

Exemplary TTI/NTI Metadata Content (2800)

The TTI/NTI Mapping Metadata Structure depicted in FIG. 26 (2600) can berepresented in a wide variety of metadata formats, but an exemplaryformat is generally illustrated in FIG. 28 (2800). Here the “keywords”tag content indicates that the metadata author/description tag contentis to be interpreted as data for the TTI/NTI mapping database. The“author” tag content defines the top level TTI associated with thecurrently presented TTI tree (which may be a branch or subbranch of someother metadata tree). The “description” tag content defines thehierarchical tree of TTI/NTI maps (which may be nested) and eventuallyresults in an atomic TTI/NTI pairing. One skilled in the art willrecognize that there are many possible syntaxes and grammars that may beused to define and interpret these exemplary metadata fields and thatthe specific grammar depicted here is only exemplary and is subject towide variation based on application context.

Several metadata examples are provided in FIG. 28 (2800). The firstexample (2810) illustrates the use of personal names (“JohnDoe”) as theTTI indexing methodology. However, the use of email addresses(“JDoe@foobar.com”) (2820) or website addresses (“www.foobar.com”)(2830) are also anticipated as potential TTI indexing methodologies.

Exemplary Metadata Grammar (2900)

While many different syntaxes/grammars may be utilized to implement theinclusion of TTI/NTI mappings within website metadata, an exemplaryExtended Backus-Naur Form (EBNF) grammar is illustrated in FIG. 29(2900). One skilled in the art will recognize that this exemplarygrammar can vary widely based on application context.

It is instructive to note that the EBNF provided in FIG. 29 (2900)incorporates “conditional” structures that permit activation of a givenNTI atom based on some conditional relation that may in some cases bedetermined by external activity (such as availability of a cellulartelephone, indications from a MICROSOFT® OUTLOOK®/GOOGLE OFFICE schedulethat an individual is in a meeting, or conditions based on calendarevents (use e-mail after 5 pm; only cellphone on weekends; only vacationcabin telephone on holidays, etc.). These conditional structures maycreate an intelligent reformation of the user interface displayspresented (FIG. 27 (2700)) in response to the realtime state of the TTD.

Exemplary NTI Atoms (3000)

Within various implementations of TTI/NTI metadata mapping, a number ofNTI atom (3010) variations are possible. Illustrative of just a few ofthese possibilities include those detailed in FIG. 30 (3000):

-   -   Numeric Telephone Numbers (3011). These may include traditional        numeric telephone number strings (“555-123-4567”) but may also        incorporate suffix modifiers to permit navigation to a specific        telephone extension (“x123”) and/or support for timed traversal        through conventional voice-driven keypad navigation (“/”)        wherein pauses are inserted as necessary to respond properly to        the timing of messages within a given voice menu context. Note        that within this context the system anticipates not only the use        of conventional DTMF codes “0123456789” but also “*” and “#” as        well as the unused but available DTMF codes for “ABCD”. This        capability permits enterprise call centers to quickly route a        caller to a given internal telephone extension without wasting        hold time or long distance charges.    -   Email Address (3012). This NTI atom variant permits an email        address to be used as the target communication link. In this        case a telephone call may be converted from voice to a digital        data stream and sent as an e-mail to the TTD.    -   Web Address (3013). This NTI atom variant permits a web address        to be used as a reference for another tree of potential TTI        references. In this manner, a set of TTI/NTI mappings not        necessarily maintained by the local metadata can be directly        included by reference.    -   TTI Reference (3014). This NTI atom variant permits a generic        TTI to be identified as a branch point for the current TTI/NTI        pair. This permits branches of other TTIs to be referenced        symbolically.    -   NTI Atom List (3015). Any of the above described atoms may be        concatenated in list form to indicate that the set represents an        equivalent (or demanded) series of communications. In other        words, it may be desirable in some circumstances to pick ONE of        the atoms in this list or in other circumstance pick the ENTIRE        list as the target for communication addressing.        One skilled in the art will recognize that this list is not        exhaustive and may vary widely based on application context.

Exemplary TTI Metadata Creation Method (3100)

While the TTI/NTI metadata mapping described above may be implementedusing manual entry of TTI/NTI data, a more preferred methodology formany enterprise implementations is the use of automated metadatacreation as generally illustrated in the flowchart of FIG. 31 (3100).Here an exemplary automated system is detailed that incorporatesmethodologies to extract TTI/NTI data from enterprise organizationalrecords (employee names, internal telephone numbers, department names,product lines, etc.) (3110) and using enterprise email addresses (3120).The general steps to this metadata creation method include:

-   -   (1) Extract TTI/NTI mapping information record from a local        enterprise organizational/phone database (3101);    -   (2) Create HTML metadata using the TTI/NTI information record        (3102);    -   (3) Inserting the HTML metadata into enterprise website content        (3103);    -   (4) Determining if there are more enterprise        organizational/phone records to process, and if so, proceeding        to step (1) (3104);    -   (5) Defining a TTI/NTI map using an enterprise email address (as        the TTI) and the corresponding telephone number associated with        the email address (as the NTI) (3105);    -   (6) Create HTML metadata using the TTI/NTI information record        (3106);    -   (7) Inserting the HTML metadata into enterprise website content        (3107);    -   (8) Determining if there are more enterprise email records to        process, and if so, proceeding to step (5) (3108); and    -   (9) Invoking a web crawler (or assuming an external web crawler        will eventually be activated) to scan the HTML metadata in the        enterprise website to generate one or more global TTI/NTI        mapping databases (3109).        As discussed above, steps (1)-(4) are generally responsible for        extracting conventional internal telephone directory information        from the enterprise and creating metadata from this information        (3110) and steps (5)-8) are generally responsible for mapping        employee/department email information to corresponding NTI        information (3120).

Note that this methodology anticipates the use of a web crawler to laterscan the HTML metadata records and populate one or more global TTI/NTImapping databases. An exemplary web crawler search method is generallyillustrated in FIG. 32 (3200) and discussed in more detail below.

Exemplary TTI Metadata Search Method (3200)

A detail of an exemplary metadata search method is provided in FIG. 32(3200), wherein the steps associated with collecting the TTI/NTI mappingmetadata include the following:

-   -   (1) Selecting the next (or first) URL/IP address for scanning        (3201);    -   (2) Determining if the URL/IP search is completed, and if so,        proceeding to step (1) (3202);    -   (3) Selecting the next (or first) file in the selected URL/IP        address for scanning (3203);    -   (4) Determining if all files on the URL/IP address have been        scanned, and if so, proceeding to step (1) (3204);    -   (5) Determining if the selected file is an HTML file, and if        not, proceeding to step (3) (3205);    -   (6) Scanning the selected file for metadata (3206);    -   (7) If TTI/NTI metadata is not found, then proceeding to        step (3) (3207);    -   (8) Loading the TTI/NTI metadata into a TTI/NTI mapping database        and proceeding to step (3) (3208).

It should be noted that selection of the URL/IP address can take severalforms, from sequentially accessing records in a master Internet domainname server (DNS) (to retrieve pairings of domain name and IP address),or by simply generating sequential IP addresses (xxx.xxx.xxx.xxx) andusing these to directly access nodes on the Internet for the purposes ofcollecting metadata.

This methodology may be implemented in a standalone fashion orintegrated within conventional web crawler search engine scanning(GOGGLE®, YAHOO®, etc.) to consolidate conventional web searchingfunctions with accumulation of TTI/NTI mapping data.

Advantages to Web-Based Mapping Metadata

A significant advantage to the use of web-based mapping metadata topopulate a more globally accessible TTI/NTI mapping database is the factthat corporations and other enterprises which maintain localizedtelecommunications infrastructures can easily update their localinformation and then have it “scraped” and integrated into any number ofglobal mapping databases that can then be accessed by a plethora ofusers on the Internet. Thus, the individual enterprise is notresponsible for maintenance of any number of TTI/NTI mapping databases,just for the localized copy that can be scanned by external webcrawlers. Within this context, search engine companies such as GOGGLE®,MICROSOFT® BINGO, YAHOO®, etc. can apply their sophisticated webcrawling technology to index, prioritize, and serve the most commonlyand closest search results of TTI/NTI and the names associated with theTTI/NTI.

This capability has significant advantages in dissemination of changesto the enterprise telecommunications infrastructure. As the NTIs withinan enterprise may change with time (as does their organizationalstructure), the enterprise need only maintain this structure in ONEplace, and then it can be replicated using web crawlers to outsideTTI/NTI mapping databases for use by external users. One skilled in theart will recognize that an application to translate internaltelephone/web addresses within an enterprise into the metadata frameworkdescribed herein would be application specific to an organization butwithin the capability of one of ordinary skill in the programming arts.

Automated TMD Generation from Website Scans (3300)-(3400) System DataFlow (3300)

In some circumstance the present invention may be implemented using anautomated methodology to create the TTI-to-NTI mapping database (TMD).As generally illustrated in FIG. 33 (3300), this can be implemented bythe TMS (3311) executing a DNS extraction process (3312) and a telephonenumber scraper process (3313). The DNS extraction process (3312)interacts with a DNS server (3321) over the Internet (3301) to gainaccess to a domain name database (3322) that details domain names astextual URL strings. These URLs are then used to access thecorresponding websites (3323) associated with the URLs. The telephonenumber scraper process (3313) then scans the website (3323) for HTMLfiles containing telephone numbers. Telephone numbers found using thisprocess that meet contextual search parameters (proximity to addressinfo, embedded metadata, placement on banner/footer of website, etc.)are then concatenated (3314) with the URL found by the DNS extractionprocess (3312) to yield a TTI/NTI mapping database (TMD) (3315) entry.

Exemplary Website Search Method (3400) A detail of an exemplary websitetelephone number search method is provided in FIG. 34 (3400), whereinthe steps associated with collecting the TTI/NTI mapping informationinclude the following:

-   -   (1) Downloading a DNS database from a DNS server to identify        URLs for telephone number searching (3401);    -   (2) Selecting the next (first) DNS list entry (URL) for website        telephone number processing (3402);    -   (3) Searching HTML files associated with the website URL for        valid telephone numbers (this may require textual filtering        based on a variety of different telephone number formats)        (3403);    -   (4) Determining if a valid detected telephone number (DPN) has        been detected in the search, and if not, proceeding to step (7)        (3404);    -   (5) Determining if the context of the DPN within the HTML is        acceptable, and if not, proceeding to step (7) (3405);    -   (6) Loading the TTI/NTI mapping database (TMD) with an entry        pair consisting of the URL (TTI)/DPN (NTI) pair (3406); and    -   (7) Determining if the DNS website list has been completely        scanned, and if not, proceeding to step (2) (3407).

This methodology may be implemented in a standalone fashion orintegrated within conventional web crawler search engine scanning(GOGGLE®, YAHOO®, etc.) to consolidate conventional web searchingfunctions with accumulation of TTI/NTI mapping data.

Automated TMD Generation from Social Media (3500)-(3600) System DataFlow (3500)

In some circumstance the present invention may be implemented using anautomated methodology to create the TTI-to-NTI mapping database (TMD)extracted from social media websites (SMW). As generally illustrated inFIG. 35 (3500), this can be implemented by the TMS (3511) executing auser profile extraction process (3512) and a telephone number scraperprocess (3513). The user profile extraction process (3512) interactswith a social media website server (SMS) (3521) over the Internet (3501)to gain access to a social media website search database (3522) thatdetails domain names and extraction methodologies for extractinginformation from a SMW. This information is then used to access thecorresponding SMW (3523) associated with the SMW URLs. The telephonenumber scraper process (3513) then scans the SMW (3523) for user profileidentifier (UPI) HTML files containing telephone numbers. Telephonenumbers found using this process that meet contextual search parameters(proximity to address info, embedded metadata, placement within specificareas of website, etc.) are then concatenated (3514) with the SMW/UIDfound by the user profile extraction process (3512) to yield a TTI/NTImapping database (TMD) (3515) entry.

Exemplary Website Search Method (3600)

A detail of an exemplary social media telephone number search method isprovided in FIG. 36 (3600), wherein the steps associated with collectingthe TTI/NTI mapping information include the following:

-   -   (1) Downloading a list of potential social media websites (SMW)        from a social media server (SMS) to identify SMW URLs (and data        extraction methodologies) for telephone number searching (3601);    -   (2) Selecting the next (first) SMW list entry (URL) for website        telephone number processing (3602);    -   (3) Searching user profile identifiers (UPI) on the SMW and HTML        files associated with the SMW URL for valid telephone numbers        (this may require textual filtering based on a variety of        different telephone number formats and SMW text        placement/display methodologies) (3603);    -   (4) Determining if a valid detected telephone number (DPN) has        been detected in the search, and if not, proceeding to step (7)        (3604);    -   (5) Determining if the context of the DPN within the SMW HTML is        acceptable, and if not, proceeding to step (7) (3605);    -   (6) Loading the TTI/NTI mapping database (TMD) with an entry        pair consisting of the SMW URL/UPI (TTI)/DPN (NTI) pair (3606);        and    -   (7) Determining if the SMW website list has been completely        scanned, and if not, proceeding to step (2) (3607).

This methodology may be implemented in a standalone fashion orintegrated within conventional web crawler search engine scanning(GOGGLE®, YAHOO®, etc.) to consolidate conventional web searchingfunctions with accumulation of TTI/NTI mapping data. This process isgenerally applicable to all social media websites such as FACEBOOK®,MYSPACE®, LINKEDIN®, and the like.

STD TTI/NTI Caching (3700)-(3800) Exemplary STD Caching System (3700)

The present invention anticipates that in some circumstances the STDand/or TTD may cooperate with the TMS to maintain TTI/NTI mappingdatabase (TMD) information locally within the context of the STD/TTDenvironment, eliminating the need for TMS access during every telephonecall initiated from the STD to the TTD.

An exemplary embodiment of such a system is generally illustrated inFIG. 37 (3700), where the STD (3720) communicates with the TMS (3711)and TMD (3713) via the computer network (3701). Here the STD (3720)maintains a local STD TTI/NTI mapping cache (3722) which is accessed viaa lookup request (3723) upon selection of a TID entry by the user. Ifthe local cache (3722) lookup response (3724) indicates that the TTI hasbeen found, it is used to generate the TTI/NTI translation and initiatethe PSTN telephone call (3725). Otherwise, the STD (3720) initiatescommunication with the TMS (3711) to request (3726) a TTI/NTItranslation with the TMS (3711) response mapping (3727) used to initiatethe telephone call (3725). Any resulting TTI/NTI mapping informationreceived from the TMS (3711) is stored (3728) within the local STD cache(3722) for use later if needed. Note that this system anticipates thatupdate messages (3729) from the TMS (3711) may be synchronously orasynchronously received by the STD (3720) to initiate cache (3722)updates when the TTI/NTI mapping database (TMD) (3713) is changed.

Exemplary STD Caching Method (3800)

A detail of an exemplary STD TTI/NTI caching method is provided in FIG.38 (3800), wherein the steps associated with the method include thefollowing:

-   -   (1) Entering a TTI for NTI translation via a STD user interface        (3801);    -   (2) Determining if a TMS update has been received for this TTI,        and if so, proceeding to step (4) (3802);    -   (3) Determining if the TTI is already in the local STD cache,        and if so, proceeding to step (8) (3803);    -   (4) Requesting a TTI lookup from the TMS (3804);    -   (5) Loading the STD local TTI/NTI mapping cache with the TTI/NTI        mapping tree retrieved from the TMS (3805);    -   (6) Determining if the TTI was found in the returned mapping        tree, and if so, proceeding to step (8) (3806);    -   (7) Issuing a “search failure” message to the STD and proceeding        to step (10) (3807);    -   (8) Translating the TTI to a resolved NTI using the local STD        mapping cache (3808);    -   (9) Processing the STD telephone call using the resolved NTI        (3809); and    -   (10) Terminating the method (3810).

This methodology may incorporate additional security/password accessrestrictions as may be required for direct access to the TMS. Theability to locally cache the TTI/NTI mappings most commonly used by theSTD may in some circumstances result in improved telephone callplacement performance. Since the TMS has knowledge of which STDs haverequested TTI/NTI mapping operations, it may maintain a list of STDsthat must be updated in response to any changes in the TTI/NTI mappingdatabase (TMD).

Automated Telecom Infrastructure Updates (3900)-(4000)

The present invention anticipates that several embodiments of thepresent invention may be advantageously applied to automatically adjustTTI/NTI mappings within the TMD in response to change orders generatedby telephone companies, telecommunication standards industries, or otherentities that have operational control over the PSTN. The purpose ofthis invention embodiment variant is to eliminate the need for customersor other telephone users to modify their telephone address books orother information that would normally incorporate a NTI.

Exemplary Automated Telecom Updating System (3900)

An exemplary system embodying this concept is generally illustrated inFIG. 39 (3900) wherein the TMS (3911), operational software (3912),TTI/NTI mapping database (TMD) (3913) and related TTI/NTI mappings(3914) operate as described above. This system is augmented with a TMSediting process (3915) that permits a remote telephone company server(TCS) (3921) executing control software read from a computer readablemedium to initiate programmed edits to the TMD (3913) based on a set ofTTI/NTI mapping database change orders (TCO) (3930). The TCOs may takemany forms, including but not limited to the following:

-   -   Country Code Changes (3931). Changes in country code (or        portions thereof) can be replaced en masse using wildcard        substitutions (“123”→“456”).    -   Area Code Changes (3932). This permits a wildcard substitution        of area codes that may include a subrange of exchanges        (“(214)-555-****”→“(972)-555-****”). This permits additional        area codes to be added with remapping of individual NTIs in a        manner that is transparent to the operation of the TTIs        associated with the original NTIs.    -   Dialing Syntax Changes (3933). Changes to the basic syntax of a        given NTI string can be substituted as necessary to accommodate        changes in a country's dialing syntax. This can occur without        the knowledge of the telephone user on either end of the        telephone link, as each party still refers to the other using        the STI/NTI arbitrary data string. While the specific syntax for        this type of change may vary widely, one skilled in the art will        recognize that this function would be easily implemented by one        of skill in the programming arts.    -   Customer NTI Forwarding (3934). When a telephone customer leaves        a geographic area served by a telephone company to an area        served by another telephone company (or moves within a        geographic area served by the same telephone company) it is        often the case that their NTI will change. This is especially        true for land line communications.

Within this context, the present invention anticipates that NTI changesassociated with a particular customer which occur due to these moves canbe reflected in a change order that automatically updates the TMD (3913)with the mapping change. Therefore, rather than receiving a message fromthe telephone company indicating that a telephone number has beenchanged, the originating caller will automatically be routed to thecorrect NTI by virtue of reference to the updated TMD (3913) whichincorporates the new customer NTI change order (3934). This TCO may alsobe applied to situations in which a business or other organization ismigrated from a singular telephone number (555-123-4567) to a privatebranch exchange (PBX) having a number of direct lines (555-999-xxxx).

-   -   Manual Telco Operations (3940). The system as described may        incorporate a telephone company (TELCO) operator interface        (3940) that permits manual changes (3941) to the TMD (3913)        and/or interfaces to telephone standards organizations (3942)        that may direct TMD (3913) changes in a more global context.        One skilled in the art will recognize that the range of change        orders (TCOs) that may be supported in this configuration is not        limited to the examples provided above.

Exemplary Automated Telecom Updating Method (4000)

A detail of an exemplary automated telecom updating method is providedin FIG. 40 (4000), wherein the steps associated with the method includethe following:

-   -   (1) Entering a telco change order (TCO) from an operator or        telco standards organization (4001);    -   (2) Generating a TMD editing script from the TCO to implement        the TCO sequentially within the TMD (4002);    -   (3) Establishing communication with the TMS over a computer        network (4003);    -   (4) Authenticating access to the TMS editing process (TME)        (4004);    -   (5) Uploading the TMD editing script to the TME (4005);    -   (6) TME locks the TMD and creates a backup copy of the TMD        (4006);    -   (7) TME sequentially applies (executes) the TMD editing script        (4007);    -   (8) If an error is not detected in TMD script execution of the        current edit step, control is passed to step (10) (4008);    -   (9) TME replaces TMD with backup TMD copy and proceeds to        step (11) (4009);    -   (10) Determining if the TMD editing script execution is        complete, and if not, proceeding to step (7) (4010);    -   (11) TME unlocks the TMD and releases the updated (or original)        TMD for use by telco consumers (4011); and    -   (12) TME report the success/error completion status of the TMD        editing script to the TCO originating entity (4012).

This methodology may be implemented in a standalone fashion orintegrated within conventional web crawler search engine scanning(GOGGLE®, YAHOO®, etc.) to consolidate conventional web searchingfunctions with accumulation of TTI/NTI mapping data.

Reverse Calling/Callback Support (4100, 4200)

In certain circumstances the present invention may incorporate “reversecallback” functionality as generally illustrated in FIG. 41 (4100) andFIG. 42 (4200). In this configuration the responsibility of initiatingthe telephone call rests with the TTD (4130) rather than the STD (4120)as generally illustrated in FIG. 41 (4100).

Exemplary Reverse Callback System (4100)

As generally illustrated in FIG. 41 (4100), the STD (4120) initiates atelephone call by making a request for TTI/NTI lookup (4122) to the TMS(4111). The TMS (4111) then sends the NTI of the STD (4132) to the TTD(4130) along with a request (4133) to the TTD (4130) to initiate a call(4134) to the STD (4120). The initiated call (4134) is then routed(4124) to the STD (4120) and the call progresses until call completion(4141).

This reverse callback feature may be advantageously utilized in manycircumstances where the cost of call initiation/completion is lower wheninitiated from the TTD (4130) rather than the STD (4120). The presentinvention anticipates that in some preferred embodiments the TMS (4111)may incorporate cost analysis software to determine the optimal cost ofcall completion and automatically select between call originator (CO)(STD) (4120) and call receiver (CR) (TTD) (4130) origination of thetelephone call.

This technique that permits the TTD to initiate the return call to theSTD rather than the STD initiating the telephone call may have advantagein situations where the TTD doesn't want the STD to have knowledge oftheir true NTI. For example, a person in witness protection might wantthe ability to be contacted, but without any ability for the calloriginator to identify their telephone number or location. This mightpermit, for example, a celebrity to create a temporary TTI and permitaccess to their phone for a set period of time but not permit callersaccess to their real NTI that they use on a daily basis. Otherapplications to secure communications are anticipated using this“reverse callback” technology.

Exemplary Reverse Callback Method (4200)

A detail of an exemplary reverse callback method is provided in FIG. 42(4200), wherein the steps associated with the method include thefollowing:

-   -   (1) The Call Originator (CO) enters the target telephone        identifier (TTI) for the Call Receiver (CR) on a source        telephone (telephone instrument device (TID)) (STD) (4201).    -   (2) The STD sends the TTI along with other relevant details such        as the caller's TTI and password to the telephone mapping server        (TMS) (4202).    -   (3) The TMS sends the numeric telephone identifier (NTI)        (telephone number, and possibly other information objects such        as pictures, logo, short messages, GPS location, GPS location        translation, etc.) of the STD to the TTD (4203).    -   (4) TTD dials the NTI to connect the CR TTD and the source TID        (STD) associated with the CO (4204).    -   (5) The telephone call is routed through the public switched        telephone network (PSTN) through the telephone company central        office (CCO) to the STD associated with the CO (4205).    -   (6) CO (if properly equipped with application specific software)        may optionally connect to TMD and get CR info such as CR TTI,        picture/logo, GPS location, GPS location translation, etc.        (cross-information transmission between TTD and STD may be        implemented) (4206).

It should be noted that TTD reverse callback in this context may be usedby the TMS (4111) to force the TTD (4130) to dial more than one STD(4120) to initiate conference calls and the like.

Collect Calls

The reverse callback methodology depicted in FIG. 41 (4100)—FIG. 42(4200) may also be used to implement “collect” calls in which the callreceiver is prompted by the TMS to initiate the call from the TTD to theSTD and thus make the TTD responsible for the calling charges. This issimilar to telephone company “collect calling” but in this situation thetelephone company is not involved in the transaction. Normally the STDis the CO and the TTD is the CR. But this role is reversed in thiscollect calling scenario where the TTD is the CO initiating the call andthe STD is a call receiver (CR) who “invites/requests” the TTD toinitiate a call. Both STD and TTD device user interface/displays mayprovide options to send and receive the request. The may be implementedby having a COLLECT CALL/ACCEPT CALL menu option on the TUI display.When the STD user selects this option then the functionality shown inFIG. 41 (4100)—FIG. 42 (4200) is initiated to make the collect call andwhen such a call is indicated on the TTD, the TTD user may either selectthe COLLECT CALL/ACCEPT CALL option or CANCEL to reject the collectcall.

Optimized Telecommunications Addressing (4300)

One skilled in the art will recognize that the method depicted in FIG.42 (4200) may be used in conjunction with the method in FIG. 2 (0200) toprovide for a telecommunications addressing method that selects between“forward dialing” (STD-to-TTD) and “reverse dialing” (TTD-to-STD) basedon a goal of minimizing expected telephone call costs associated withthe selected call completion technique. This method as depicted in FIG.43 (4300) generally comprises the following steps:

-   -   (1) The Call Originator (CO) enters the target telephone        identifier (TTI) for the Call Receiver (CR) on a source        telephone (telephone instrument device (TID)) (STD) (4301).    -   (2) The STD sends the TTI along with other relevant details such        as the caller's TTI and password to the telephone mapping server        (TMS) (4302).    -   (3) The TMS determines the lowest cost telephone call using        forward/reverse dialing techniques (4303).    -   (4) If the lowest cost telephone call is a reverse call, control        is passed to step (6) (4304).    -   (5) FORWARD calling is utilized invoking steps (3)-(5) in FIG. 2        (0200) and control is passed to step (7) (4305).    -   (6) REVERSE calling is utilized invoking steps (3)-(5) in FIG.        42 (4200) (4307).    -   (7) CO (if properly equipped with application specific software)        may optionally connect to TMD and get CR info such as CR TTI,        picture/logo etc. (cross-information transmission between TTD        and STD may be implemented) (4307).

It should be noted that this optimized calling procedure may permitmultiple STDs to communicate with multiple TTDs in conference calls andthe like as was previously discussed in the call forward and callreverse cases discussed previously.

Queued Telecommunications Addressing (4400)-(4800)

In any of the scenarios in which the present invention may beimplemented the system/method may incorporate methodologies to supportqueued addressing of the TTD. In this manner, a TTD may manage a “queue”of incoming calls from various STDs and prioritize the order of thecommunications that occurs between the TTD and the STDs. Incoming callsfrom various STDs may be given priorities by the TTD based on TTIsand/or NTIs associated with the incoming calls. Furthermore, the STDsmay be notified by the TMS of their priority, queue index (number ofhigher priority calls), and estimated wait time for connection to theTTD.

Exemplary Queued Telecommunication System (4400, 4500)

An exemplary system embodiment of this as applied to forward callprocessing is generally illustrated in FIG. 44 (4400) which generallyparallels FIG. 1 (0100) (a corresponding parallel to the reversecallback system in FIG. 41 (4100) is generally provided in FIG. 45(4500)). Here the TTD (4430) incorporates a call queue (4435) that ismaintained to order incoming call requests from the TMS (4411). The TTD(4430) prioritizes the incoming call request (4432) and returns the STDqueue priority (4433) to the TMS (4411). The TMS (4411) then returns theNTI (4423) along with this information (4425) to the STD (4420) andcoordinates call initiation (4424) when the STD has been dequeued (madeactive) by the TTD (4430). Information regarding the call queue waittime (4423) and other information regarding the status of the TTD (4430)may be communicated to the STD (4420) to permit optimum allocation oftime and resources on the STD (4420) during the pendency of thetelephone call request to the TTD (4430). A similar system scenario isdepicted in FIG. 45 (4500) with the exception that the call initiation(4534) is done by the TTD (4530) rather than the STD (4520).

Note that in both scenarios depicted in FIGS. 44 (4400) and 45 (4500)the call between the STD-to-TTD (FIG. 44 (4400)) or TTD-to-STD (FIG. 45(4500)) is not necessarily initiated until the STD request forcommunication has been dequeued for active service by the TTD (4430,4530). This means that there is no need to add to telephone congestionwithin the PSTN (4440, 4540) during the wait time for communicationsinitiation. This can greatly reduce the susceptibility of the PSTN(4440, 4540) to overload failures during peak demand events (naturaldisasters, etc.) and provide an orderly methodology of processingincoming calls to the TTD during periods of “impulse” demand.

These systems may as described herein also be integrated withcalendaring software on the TTD and/or STD to schedule a time forservice of the STD-initiated call by the TTD. Thus, one potentialresponse for the STD call initiation to the TTD is for the TTD and/orSTD to negotiate a time in the future to initiate the actual telephonecall if at present the parties cannot agree on communicating.

Exemplary Queued Telecommunication Addressing Method (4600)

A detail of an exemplary queued telecommunication addressing method isprovided in FIG. 46 (4600), wherein the steps associated with the methodinclude the following:

-   -   (1) The Call Originator (CO) enters the target telephone        identifier (TTI) for the Call Receiver (CR) on a source        telephone (telephone instrument device (TID)) (STD) (4601).    -   (2) The STD sends the TTI along with other relevant details such        as the caller's TTI and password to the telephone mapping server        (TMS) (4602).    -   (3) The TMS communicates with the TTD to send a request for STD        communication to the TTD (4603).    -   (4) The TTD prioritizes and queues the STD request for a        telephone call (4604).    -   (5) The TMS communicates with the TTD to determine the current        TTD caller queue depth (4605).    -   (6) The TMS communicates the current TTD caller queue status to        the STD (4606).    -   (7) The TMS waits for the STD to become dequeued (currently        active) on the TTD caller list (4607).    -   (8) The TMS coordinates call initiation/completion from the        STD-to-TTD (forward calling using FIG. 2 (0200)) or TTD-to-STD        (reverse calling using FIG. 42 (4200)) (4608).

One skilled in the art will recognize that information in the TMDrelating to the TTIs of the STD and/or TTD may be used within thisprocess to prioritize the call within the TTD call processing queue.This information may (for example) be used to raise the priority of callprocessing for some incoming calls dynamically based on informationheld/maintained by the TMD. This might have application in situationswhere calls are “escalated” within the technical support centersoperated within the context of TTD call centers.

As mentioned previously, this method may incorporate calendaringfunctions to schedule calls between the STD and TTD based on mutuallyagreeable times defined either by the users or automatically determinedby the TMS after scanning calendar information provided by the STD andTTD.

Exemplary Incoming Call Queue Display (4700)

As generally depicted in FIG. 47 (4700), some preferred inventionembodiments may utilize an incoming call queue prioritization userinterface that permits TTD incoming calls to be displayed for inspectionand review. This user interface may have many forms, but in somepreferred embodiments may incorporate a list of TTIs that are queued forcommunication with the TTD along with their TTI/NTI information,processing priority, hold time, etc. This information may be updated bythe TTD user and used to select a given incoming STD call for processingimmediately, or optionally scheduled for processing later using acalendaring function. The calendaring function may operate to coordinatecalendars on the STD and TTD to accommodate a mutually agreeable time;it may select from meeting times proposed by the STD; or it may selecttime slots available on the TTD and send this information back to theSTD for confirmation of a fixed call initiation time.

This incoming call queue display function is a significant improvementover conventional “call waiting” technology implemented in currenttelephones for several reasons, including but not limited to:

-   -   Unlike conventional “call waiting,” any number of TTD incoming        calls may be queued for processing (and later connection through        the PSTN) without the need for the telephone call to be        processed by the PSTN at the time the call is queued.    -   Calls may be prioritized by the STD, the TTD, and information        stored in the TMD that associates a “baseline” priority for the        STD-TTD communication link.    -   The prioritization of incoming calls is dynamic and capable of        queue priority reordering as incoming calls are processed.    -   TTDs connected to PSTN infrastructure that supports “call        waiting” may support TWO incoming queues (one for each ‘virtual’        telephone line in the call waiting infrastructure).    -   While the TTD may receive calls from any number of STDs, each        STD may have initiated the call to the TTD using a different        TTI, allowing prioritization of incoming calls using TTI        differentiation. For example, TTIs for “ACME Service—Warranty        Repair” and “ACME Service—Critical Machine Down!” may resolve to        the same TTD, but with different service priorities.    -   Unlike conventional “call waiting” support in the PSTN, the        incoming call queue display never issues a “busy” signal to the        STD initiating the call. Rather, the call can be queued for        processing or scheduled for a callback by the TTD.    -   Unlike conventional “call waiting” support in the PSTN, the        incoming call queue display has full knowledge of all incoming        calls from any STD, not just a single “call waiting” STD.        One skilled in the art will recognize that this list is        non-exhaustive and only exemplary of the benefits of call        queuing as taught by the present invention.

Exemplary Outgoing Call Queue Display (4800)

As generally depicted in FIG. 48 (4800), some preferred inventionembodiments may utilize an outgoing call queue status user interfacethat permits STD outgoing call status to be displayed. This userinterface may have many forms, but in some preferred embodiments mayincorporate a list of TTIs that are queued for communication with theSTD along with their TTI/NTI information, current queue priority, holdtime, expected call initiation time, etc.

This status display may permit the STD to leave a voicemail message (inaddition to their TTI/NTI information) as well as opt for alternate callprocessing by the TTD (escalated call processing to the nextadministrative level within the TTI hierarchy). As with the TTD display,this status display may permit a scheduled call initiation time to bedetermined by the STD as a request for STD-to-TTD communication to occurat a specific time (or range of times) in the future.

Calendaring Interface (4900)-(5000)

As generally illustrated in FIG. 49 (4900), the present inventionanticipates that the TMS (4911) may interface with a computing device(4920) (desktop, laptop, tablet, mobile device, STD, TTD, etc.) thatincorporates some form of calendaring software (4921). This TMS (4911)TTI Application Software I/F (4922) interfaces with the calendaringsoftware (4921) in real-time and reads status information (regardingmeetings/out-of-office/busy, etc.) on user schedules and updates TTIcalendaring profiles (4914) within the TMD (4913).

An exemplary user interface for the TTI application software (4922) isdepicted in FIG. 50 (5000). As with call blocking and call restriction(parental control) functionality, the TMS may check the call schedulebefore routing calls to “Dr. John Howard”. This check is generallyperformed for all call recipients. As depicted, entries on this userinterface page can be made directly by the account holder after loggingin by using add/delete options options/buttons on the page or entriescould be added/deleted by remote software described in FIG. 49 (4900).One skilled in the art will recognize that this user interface could beintegrated within application calendaring software (4921) rather thanimplemented as a separate application (4922). The default option forcall receivers is that they are available and will receive calls unlessotherwise restricted or blocked.

Note that call forwarding in this context may be used to dynamicallyforward calls based on TTI. In the example depicted in FIG. 50 (5000),STDs attempting to contact the TTI ‘DRJH’ will be redirected to the TTI‘JHWKNDHM’ (Dr. John Howard's weekend home) during the period of thespecified vacation. This methodology of dynamically redirecting callscan be used to time screen calls and/or ensure that important calls areproperly redirected to a TTD that may be accessed by the call receiver.

Call Initiation/Integration Interface (5100)

In some circumstances the present invention may be integrated as aplug-in or add-on to existing software within a computing device asgenerally illustrated in FIG. 51 (5100). Here a computing device (5120)(desktop, laptop, tablet, mobile device, STD, TTD, etc.) may incorporatehost software (5121) that may comprise a web browser or other hostsoftware that has knowledge of TTI/NTI data associated with the STDowner. This host software (5121) may be augmented with a plug-in/add-on(5122) that has knowledge of the TTI and/or password associated with theSTD, and may be used to interface the computing device (5120) to the TMS(5111) for the purposes of performing TTI/NTI translations (5114) usingthe TMD (5113).

The TMS (5111) receives the STD TTI and/or password from the STD (5120)along with the TTI of the selected call recipient and sends thisinformation to the TMS (5111) for translation against the TMD (5113).Scheduling software (5115) within the TMS (5111) then directs callinitiation between the STD and TTD if no scheduling conflict exists andthe STD call processing is initiated.

This scenario illustrates that existing computing platforms (5120)having a wide variety of host applications can be augmented with TTIapplication software (5122) that can interface with the TMS (5111) andaffect operation of the invention in a wide variety of applicationcontexts.

Parental Controls/Call Restrictions (5200)-(5300) Parental Controls/CallRestrictions Dialog (5200)

The TMS in processing telephone calls between the STD and TTD may insome embodiments implement parental controls/call restrictionsfunctionality in which outgoing and/or incoming calls associated withthe STD and/or TTD may be restricted to particular TTIs (or TTI trees).An exemplary user interface dialog implementing this functionality isgenerally depicted in FIG. 52 (5200) wherein outgoing calls may beblocked (5201) within a dialog definition (5202) as well as incomingcalls may be blocked (5203) within a corresponding dialog definition(5204). Entries may be added (5205, 5206) or removed (5207, 5208) fromthese restriction lists as necessary. This exemplary dialog permitsspecification of the call restrictions based on TTI and/or NTI asdesired. Note that the present invention anticipates that parentalcontrols may permit only specific outgoing calls and/or specificincoming calls. Other variations of this call permission/blockingmethodology may permit TTI trees of outgoing calls or TTI trees ofincoming calls or the selection of TTI trees that may be specificallyblocked.

Once the call restriction list is defined as indicated in FIG. 52(5200), this information is stored in the TMD and used by the TMS todetermine if a given telephone call is to be processed/completed.

Parental Controls/Call Restrictions Method (5300)

The above described parental control/call restriction system may operatein conjunction with a corresponding method as depicted in FIG. 53 (5300)comprising the following steps:

-   -   (1) requesting a telephone call between the STD and the TTD        using a STD-supplied TTI that is sent to the TMS (5301);    -   (2) searching the TMD with the TMS for STD TTI outgoing allowed        call data (5302);    -   (3) determining if the outgoing call is allowed, and if so,        proceeding to step (5) (5303);    -   (4) rejecting the TTI map request and sending a message to the        STD indicating the outgoing call is blocked and proceeding to        step (11) (5304);    -   (5) searching the TMD with the TMS for TTD TTI incoming allowed        call data (5305);    -   (6) determining if the incoming call is allowed, and if so,        proceeding to step (8) (5306);    -   (7) rejecting the TTI map request and sending a message to the        STD indicating the incoming call is blocked and proceeding to        step (11) (5307);    -   (8) translating the STD/TTD TTI using the TMS and TMD to        generate an associated TTD/STD NTI (this translation may vary        based on whether the telephone call processing uses forward or        reverse dialup procedures) (5308);    -   (9) initiating the telephone call between the STD/TTD using the        translated TTD/STD NTI (5309);    -   (10) routing the telephone call through the PSTN between the STD        and TTD (5310); and    -   (11) processing the telephone call to completion (5311).

As can be seen from this general procedure, parental controls may beimplemented to allow only specific outgoing calls from the STD telephoneand/or allow only specific incoming calls to the STD telephone. Thisgeneral method summary may be augmented by the various elementsdescribed herein to produce a wide variety of invention embodimentsconsistent with this overall design description.

Call Location Identification (5400)-(5600)

The present invention anticipates that in some preferred embodiments thelocation of one or more of the TIDs associated with a telephone call maybe displayed on other TIDs associated with the telephone call. Forexample, current mobile phones display the STD's phone number along withtheir phone location on the TTD's display. This location is based onwhere the STD phone number was registered with the telephone companiesor the STD person's address registered with the phone company. This isoften misleading, because the STD's actual physical location at the timeof placing call could be anywhere in the world. For example, while the732 area code is associated with central New Jersey, a person who has a732 area code phone number would show up as Somerset N.J. on the TTD'sphone.

The present invention anticipates that GPS information associated with aTID may be used to provide other persons associated with the telephonecall with information regarding the location of the other telephone callparticipants. The present invention anticipates that the STD willcommunicate their actual physical location to the TMS at the time thetelephone call is initiated. This information about STD will be sent tothe TTD along with other information such as the STD TTI, a picture/logoassociated with the STD, etc. Similarly, the TTD may also communicateit's actual physical location to the TMS and the TMS may provide thisinformation to the STD. In this manner both the STD and TTD will knoweach other actual physical location at the time of the telephone call.

This feature is extremely useful for parents who would want to keeptrack of where their children are located when they call them. Thisfeature would also allow companies to keep physical track of theiremployees who travel as part of their work duties (e.g., salesmen,delivery men, drivers, etc.).

It is anticipated that in many preferred invention embodiments the TMSwill contain a STD/TTD user profile allowing the call locationinformation to be blocked if this feature is disabled by the STD/TTDuser.

Exemplary Call Location Identification System (5400)

An exemplary system embodiment of the present invention implementingcall location identification is generally illustrated in FIG. 54 (5400).Here the call processing generally mimics other system embodiments (asdepicted in FIG. 2 (0200), FIG. 4 (0400), FIG. 42 (4200), FIG. 43(4300), FIG. 46 (4600) and elsewhere herein). However, in this preferredembodiment the STD (5420) transmits its GPS location (5422) to the TMS(5411) which then translates this information to a STD GPS text stringvia lookup in the TMD (5413) (or some other database) and transmits thisSTD GPS text string (5432) to the TTD (5430) for display. Similarly, theTTD (5430) transmits its GPS location (5433) to the TMS (5411) whichthen translates this information to a TTD GPS text string via lookup inthe TMD (5413) (or some other database) and transmits this TTD GPS textstring (5423) to the STD (5420) for display.

Within this context the database lookup (5413) may incorporate a varietyof GPS text mapping strings (5414) that are user-defined or defined interms of known geographical landmarks (e.g., “near Statue of Liberty,NYC”). Within this context the TMD (5413) may incorporate flags toindicate “LOCATION BLOCKED” for either the STD and/or TTD to disablethis call location identification feature. This GPS location blockingfeature may also be in some instances enabled in the applicationsoftware running on the STD (5420) or the TTD (5430).

Exemplary Call Location Identification Method (5500)

The present invention preferred exemplary call location identificationmethod embodiment anticipates a wide variety of variations in the basictheme of implementation, but can be generalized as depicted in FIG. 55(5500) as a telecommunications addressing method, the method operatingin conjunction with a telecommunications addressing system, the systemcomprising:

-   -   (a) telephone mapping server (TMS);    -   (b) telephone mapping database (TMD);    -   (c) source telephone instrument device (STD);    -   (d) target telephone instrument device (TTD); and    -   (e) computer communication network (CCN);    -   wherein    -   said TMS is configured to store information that identifies a        telephone instrument device (TID) in said TMD;    -   said TMS is configured to locate a numeric telephone identifier        (NTI) within said TMD using a target telephone identifier (TTI)        data string as the locating index;    -   said NTI permits said TID to be accessed via a public switched        telephone network (PSTN); and    -   said TMS is configured to initiate a telephone call via said        PSTN between said STD and said TTD using said NTI;    -   wherein the method comprises the steps of:    -   (1) initiating and/or routing a telephone call between the STD        and TTD (as generally depicted in any of FIG. 2 (0200), FIG. 4        (0400), FIG. 42 (4200), FIG. 43 (4300), FIG. 46 (4600) and        elsewhere herein) (5501);    -   (2) sending the STD GPS location from the STD to the TMS (5502);    -   (3) determining if the STD is flagged as LOCATION BLOCKED in the        TMS, and if so, proceeding to step (6) (5503);    -   (4) translating the STD GPS location within the TMS using the        TMD as a translation database into a STD GPS text string and        transmitting this text string to the TTD (5504);    -   (5) displaying the STD GPS text string on the TTD (5505);    -   (6) sending the TTD GPS location from the TTD to the TMS (5506);    -   (7) determining if the TTD is flagged as LOCATION BLOCKED in the        TMS, and if so, proceeding to step (10) (5507);    -   (8) translating the TTD GPS location within the TMS using the        TMD as a translation database into a TTD GPS text string and        transmitting this text string to the STD (5508);    -   (9) displaying the TTD GPS text string on the STD (5509);    -   (10) process and complete the telephone call between the STD and        the TTD (5510).

This general method summary may be augmented by the various elementsdescribed herein to produce a wide variety of invention embodimentsconsistent with this overall design description.

Exemplary Call Location Identification Dialog (5600)

An exemplary call location identification dialog screen is generallyillustrated in FIG. 56 (5600). Here it can be seen that the calleroriginator (CO) TTI is indicated (“PSMT”) as well as the translated GPSlocation text string information (“455 5th Avenue, New York, N.Y.”) inaddition to a cross-referenced user-defined label associated with theGPS text string (“[HOME]”). This ability to user-define certain GPSlocations with a variety of additional text identifiers is useful inmany circumstances where the call receiver is unfamiliar with thespecific GPS location identifiers and the caller wishes to impartadditional information in the GPS text string display.

Note that while FIG. 56 (5600) illustrates a typical TTD call receiver(CR) display, a corresponding display may be associated with the STDcall originator (CO). With appropriate access controls contained in theTMD, the TMS may manage which TIDs may receive GPS information dependingon user access controls defined within the TMD.

The TMD may also incorporate distance modifiers defined by a given TIDthat may be associated with a given user-defined GPS text strings. Forexample, “near” may be associated with a distance of 100 yards, makingthe display read “near HOME” if the TID was within this range but notprecisely identified with the GPS location associated with “HOME.” Thepresent invention anticipates that polygonal regions may be associatedwith these distance modifiers to define spatial regions that can beassociated with a given GPS text string. For example, a polygonal regionmay be associated with a park or other recreational facility and theresulting GPS text string might read “within PARK” to indicate thislocation state.

Exemplary Telephone User Interface (5600)

It should be note that the various STD/TTD telephone user interface(TUI) can take many forms and incorporate many features. Exemplary TUIscreens depicted in FIG. 9 (0900)-FIG. 12 (1200), FIG. 47 (4700), FIG.48 (4800), FIG. 50 (5000) may also incorporate additional features asdepicted in FIG. 56 (5600), including but not limited to MUTE, SPEAKERPHONE, CONFERENCE CALL, KEYPAD/KEYBOARD, and CALL RECORDING functions.

Reverse TTI Lookup (5700)-(5900) Exemplary Reverse NTI Lookup SystemEmbodiment (5700)

As generally illustrated in FIG. 57 (5700), the present invention mayalso be implemented in a manner supporting “reverse” TTI lookup. In thisconfiguration, a STD (5720) may initiate a telephone call to a TTD(5730) using a conventional numeric telephone identifier (NTI)(“telephone number”) via a telephone call TTD NTI request (5722) to theTMS (5711). This TTD NTI request is then used in a “reverse lookup”fashion within the TMD (5713) to determine a TTI tree map (5714)associated with the TTD NTI. This resolved TTD TTI is then returned(5723) to the STD (5720) to allow review of the various calling optionspossible that are associated with the TTD NTI originally submitted bythe STD (5720).

This has many useful applications in situations where a business orcompany has a main branch telephone number that may be widelydistributed and published, but also hundreds (or thousands) of telephoneextensions associated with this main telephone number. By allowing thereverse lookup procedure, the TMS (5711) allows the STD (5720) toinspect which of the various telephone extensions or other companybranches are a best fit for the target of the telephone call. Once thisreturned TTD TTI list is inspected and a target TTI selected within thisTTD TTI tree, the telephone call can be completed using the othertechniques taught by the present invention and discussed herein. Ofsignificance to the TTD in this scenario is the possibility of reducingthe number of telephone operators necessary to handle a large volume ofincoming calls, as the call routing in this scenario is handledautomatically by the TMS (5711) in conjunction with the TMD (5713).

A similar scenario may be utilized from the TTD (5730) perspective inwhich the TTD (5730) may receive a call having a particular STD CALLERID telephone number. This STD NTI may be sent via a request (5732) tothe TMS (5711) and a reverse lookup performed in order to obtain areturned TTI of the STD NTI (5733). This allows the TTD to populatelocal information regarding remote callers from a trusted database (theTMD (5713)) without the TTD (5730) having any knowledge of the TTI/NTIreverse mapping data (5714) or the capability of performing a reverselookup of the TMD (5713) using information local to the TTD (5730).

Exemplary Reverse TTD-NTI Lookup Method Embodiment (5800)

As generally illustrated in FIG. 58 (5800) a preferred exemplary methodembodiment implementing reverse TTD-NTI lookup (where the STD providesthe NTI for reverse lookup) comprises the following steps:

-   -   (1) entering a NTI from the call originator (CO) STD (5801);    -   (2) transmitting the NTI to the TMS (5802);    -   (3) performing a reverse lookup on the NTI with the TMS using        data in the TMD (5803);    -   (4) translating the TTI tree associated with the NTI to the STD        (5804);    -   (5) displaying the TTI tree on the STD and enabling user        selection (5805);    -   (6) selecting an atomic element within the TTI for dialing by        the STD (5806);    -   (7) transmitting the selected TTI to the TMS for telephone call        processing (5807); and    -   (8) processing the selected target telephone call with the TMS        (using procedures outline elsewhere herein) (5808).

This technique also permits the STD to “punch down” into TTI treesassociated with businesses and other entities in order to directlyselect the target telephone identifier (TTI) associated with theintended target of the telephone call, thus eliminating the need foroperators and other intervening parties during the telephone connection.This general method summary may be augmented by the various elementsdescribed herein to produce a wide variety of invention embodimentsconsistent with this overall design description.

Exemplary Reverse STD-NTI Lookup Method Embodiment (5900)

As generally illustrated in FIG. 59 (5900) a preferred exemplary methodembodiment implementing reverse STD-NTI lookup (where the TTD providesthe NTI for reverse lookup using CALLER ID data) comprises the followingsteps:

-   -   (1) CALLER ID information sent to the call receiver (CR)        provides a NTI for the STD (5901);    -   (2) TTD sends the STD NTI to the TMS for reverse translation        (5902);    -   (3) TMS performs a reverse lookup translation using the STD NTI        (5903);    -   (4) TMS sends the translated STD TTI associated with the STD NTI        to the TTD (5904);    -   (5) TTD displays the TTI information associated with the STD NTI        (5905);    -   (6) TTD permits TTD user to select call function appropriate to        STD TTI content (accept/reject/voicemail/block calls        permanently/etc.) (5906); and    -   (7) processing the selected target telephone call with the TMS        with the user-selected call processing options (using procedures        outline elsewhere herein) (5907).

This technique allows the TMS to serve as a “gateway” screening functionfor incoming calls to the TTD by displaying information associated withthe STD that allows the TTD user to prioritize and/or redirect theaction to be associated with the STD call originator. This informationis far more descriptive than that possible with conventional CALLER IDbecause in many cases only the telephone number is available with CALLERID and as such other information associated with the STD caller is notavailable to the TDD user when using CALLER ID alone. This generalmethod summary may be augmented by the various elements described hereinto produce a wide variety of invention embodiments consistent with thisoverall design description.

Outgoing Message (OGM) (6000)-(6200)

The present invention anticipates that since the identity of theincoming caller can be known with some certainty by virtue ofinformation obtained by the TTI/NTI translation and informationcontained within the TMD (as translated by the TMS), it is possible forcalls that are processed by voicemail or other automated greetings to betailored to individual STDs and their associated TTIs.

Exemplary OGM System Embodiment (6000)

This invention embodiment variation is depicted in FIG. 60 (6000), wherethe STD (6020) initiates a request for telephone communication (6022) tothe TTD using an associated TTI. Assuming that the call cannot beprocessed (either because the TTD (6030) is unavailable or hasblocked/voicemailed the call), the TMS (6011) may opt to utilize TTI/NTIoutgoing message (OGM) data (6014) within the TMD (6013) that isprovided by the TTD (6040) and which may be specifically indexed to theSTD (6020) to return an OGM (6023) to the STD (6020). For example theSTD TTI “John Doe” may be associated with an outgoing message stating“Hello John! Sorry I can't speak with you now, but feel free to come bythe office if you have time today.” This OGM information may incorporatevoice, text data, images, video, and the like to provide a full functionmultimedia feedback to the STD (6020) in response to a call that cannotbe completed.

The call request to the TTD (6032) issued by the TMS (6011) may also beresponded to by the TTD (6030) with a local OGM or TMD OGM index (6033)that is linked to OGM data (6014) stored in the TMD (6013). Thus, thepresent invention anticipates that OGM information may be stored eitherlocally within the TTD (6030) or within the TMD (6013) (or otherancillary database). The present invention also anticipates that OGMdata may be resident on the Internet and referenced with hyperlinks orother like data references.

The present invention anticipates that the TTD (6030) may incorporatescript substitutions within the OGM data stream to permit insertion ofSTD/TTD TTI specific information or other information gathered fromcalendaring or other office productivity software. For example, the OGMvoice stream may be formed as “I am sorry <TTI_name>, but I can't cometo the phone right now. Please leave a message.” Which would vocallysubstitute the STD caller's name for the <TTI_name> token. Similarly,other tokens including GPS location information (“I′m currently at ourfield office”), scheduling conflicts (“I′m in a scheduled meeting rightnow”) may also be automatically inserted into the returned OGM. Thus,the OGM data stream is anticipated to incorporate a wide variety ofstate and context information in an attempt to formulate the OGM in anergonomic and pleasant form for the STD call originator.

Exemplary OGM Method Embodiment (6100)

As generally illustrated in FIG. 61 (6100) a preferred exemplary methodembodiment implementing outgoing message (OGM) processing comprises thefollowing steps:

-   -   (1) requesting via the STD a telephone call to the TTD by        sending a TTI for the TTD to the TMS (6101);    -   (2) attempting to complete TTI/NTI translation via the TMS and        determine if the TTD is available for telephone call (6102);    -   (3) determining if the TTD is available for the telephone call,        and if so, proceeding to step (8) (6103);    -   (4) searching the TMD for a STD/TTD TTI associated OGM (6104);    -   (5) determining if an OGM is found in the TMD, and if not,        proceeding to step (7) (6105);    -   (6) transmitting the retrieved OGM found in the TMD to the STD        (6106);    -   (7) delaying/rejecting the call completion on the STD and        updating the STD status display then proceeding to step (11)        (6107);    -   (8) translating the STD/TTD TTI to a TTD/STD NTI via the TMS        (6108);    -   (9) initiating a telephone call between the STD/TTD using the        NTI as directed by the TMS (6109);    -   (10) routing/processing the selected target telephone call with        the TMS (using procedures outline elsewhere herein) (6110);    -   (11) terminating the OGM call processing method (6111).

This technique may also be modified slightly to permit ringtones uniqueto a given STD TTI to be issued to the TTD prior to actually connectingthe STD/TTD via a telephone call. This may permit the TTD sufficienttime to STALL/DECLINE the STD telephone connection. Note that step (7)in this method may incorporate default OGMs for voicemail and otheruser-defined default call uncompleted information to be sent to the STD.This general method summary may be augmented by the various elementsdescribed herein to produce a wide variety of invention embodimentsconsistent with this overall design description.

Exemplary OGM User Dialog (6200)

An exemplary user interface dialog supporting OGM functionality isgenerally illustrated in FIG. 62 (6200). Here it can be seen that OGMsmay be associated with individual TTIs or may be generalized to astandardized OGM for TTIs that do not match a specific pattern. Supportfor matching OGMs to TTI trees or branches is also anticipated assupported within this context.

Note that within some implementation of the incoming call queueingcapability described herein there may be situations in which theincoming call is queued but not sent to voicemail. In these situationsthere may be a an “introductory message” that is conveyed to the STDmuch like a voicemail message but this message would provide additionalinformation (call queue time, other options, etc.). The differencebetween this and a normal telephone call sent to a call center would bethat the telephone call would not yet be initiated between the STD andTTD, but rather these messages would be delivered digitally (or storedon the STD) and thus bypass the normal PSTN infrastructure.

Note that this dialog may be utilized with slight modification tosupport individual RINGTONES that are associated with individual TTIs(or TTI trees/branches). While this dialog is not illustrated, oneskilled in the art would easily be able to duplicate/modify the OGMdialog to implement this functionality.

Multiple Mapping Servers/Databases (6300)-(6400)

As generally illustrated in FIG. 63 (6300), the present invention mayutilize multiple TTI/NTI mapping servers (6311, 6312) in conjunctionwith one or more TMD (6313) data arrays to implement the functionalitydescribed herein on a national, continental, and/or worldwide basis.

Similarly, as depicted in FIG. 64 (6400), the present inventionanticipates that one or more TMS systems (6411) may have associated anumber of TMD (6413, 6414) data stores that may be used to indexindividual TTI trees in support of TTI mapping on a national,continental, and/or worldwide basis.

These multiplicative TMS/TMD systems may operate in a coordinatedfashion to ensure that TTI data is both secure and reliably accessed aswell as providing the necessary bandwidth and data coherency to supportoperation of the telecommunications addressing system/method on anenterprise/worldwide basis. This architecture also permits varioustelecommunication providers (telephone companies) to individuallysupport TTI/NTI mapping functions for their customers and yet cooperatewith other telecommunication providers who also support thisfunctionality within their telecommunications networks.

Preferred Embodiment System Summary

The present invention preferred exemplary system embodiment anticipatesa wide variety of variations in the basic theme of construction, but canbe generalized as a telecommunications addressing system comprising:

-   -   (a) telephone mapping server (TMS);    -   (b) telephone mapping database (TMD);    -   (c) source telephone instrument device (STD);    -   (d) target telephone instrument device (TTD); and    -   (e) computer communication network (CCN);    -   wherein    -   said TMS is configured to store information that identifies a        telephone instrument device (TID) in said TMD;    -   said TMS is configured to locate a numeric telephone identifier        (NTI) within said TMD using a target telephone identifier (TTI)        data string as the locating index;    -   said NTI permits said TID to be accessed via a public switched        telephone network (PSTN); and    -   said TMS is configured to initiate a telephone call via said        PSTN between said STD and said TTD using said NTI.

This general system summary may be augmented by the various elementsdescribed herein to produce a wide variety of invention embodimentsconsistent with this overall design description.

Preferred Embodiment Method Summary

The present invention preferred exemplary method embodiment anticipatesa wide variety of variations in the basic theme of implementation, butcan be generalized as a telecommunications addressing method, the methodoperating in conjunction with a telecommunications addressing system,the system comprising:

-   -   (a) telephone mapping server (TMS);    -   (b) telephone mapping database (TMD);    -   (c) source telephone instrument device (STD);    -   (d) target telephone instrument device (TTD); and    -   (e) computer communication network (CCN);    -   wherein    -   said TMS is configured to store information that identifies a        telephone instrument device (TID) in said TMD;    -   said TMS is configured to locate a numeric telephone identifier        (NTI) within said TMD using a target telephone identifier (TTI)        data string as the locating index;    -   said NTI permits said TID to be accessed via a public switched        telephone network (PSTN); and    -   said TMS is configured to initiate a telephone call via said        PSTN between said STD and said TTD using said NTI;    -   wherein the method comprises the steps of:    -   (1) entering a TTI via a user interface on the STD;    -   (2) transmitting the TTI to the TMS via the CCN;    -   (3) indexing the TTI within the TMD to retrieve the NTI        associated with the TTI;    -   (4) transmitting the NTI to the STD through the CCN; and    -   (5) initiating a telephone call through the PSTN from the STD to        the TTD using the NTI.

This general method summary may be augmented by the various elementsdescribed herein to produce a wide variety of invention embodimentsconsistent with this overall design description.

System/Method Variations

The present invention anticipates a wide variety of variations in thebasic theme of construction. The examples presented previously do notrepresent the entire scope of possible usages. They are meant to cite afew of the almost limitless possibilities.

This basic system and method may be augmented with a variety ofancillary embodiments, including but not limited to:

-   -   An embodiment wherein the CCN comprises the Internet.    -   An embodiment wherein the TMS is configured to initiate the        telephone call via the PSTN from the STD to the TTD.    -   An embodiment wherein the TMS is configured to initiate the        telephone call via the PSTN from the TTD to the STD.    -   An embodiment wherein the CCN comprises a wireless communication        network.    -   An embodiment wherein the TMS comprises a computer server        contained within the PSTN.    -   An embodiment wherein the TMD comprises graphical images        associated with the TTI/NTI mappings.    -   An embodiment wherein the TMD comprises call sequencing        information associated with the TTI/NTI mappings.    -   An embodiment wherein the TMD comprises a hierarchical directory        of TTI/NTI mappings.    -   An embodiment wherein the TMD associates a plurality of the NTIs        contained within a hierarchical directory with the TTI.    -   An embodiment wherein the TMS returns the NTI based on current        TTD status information contained within the TMD that is        associated with the TTI.    -   An embodiment wherein the TMS transmits a tree of hierarchical        directory TTI/NTI mappings to the STD in response to a TTI        lookup request received from the STD.    -   An embodiment wherein the TMS is configured to communicate with        the STD via a TTI lookup software application resident on the        STD.    -   An embodiment wherein the TMS is configured to host a web        application configured to permit configuration of the TMD via a        web browser application operational on the STD.    -   An embodiment wherein the TTI comprises a data string selected        from a group consisting of: data derived from a voice        recognition software application resident on the STD; email        address; website URL address; and hierarchical path of TTI        atomic elements.    -   An embodiment wherein the TMD comprises data selected from a        group consisting of: information extracted from an enterprise        employee information database; information obtained by scanning        metadata extracted from a website HTML file; information        obtained by scanning metadata extracted from a social media        website.    -   An embodiment wherein the TMS comprises a TMD editor

(TME) configured to permit remote modification of records within the TMDspecified by a TMD editing script generated in response to a series ofchange orders (TCOs) received from a telephone company or telephonestandards organization.

-   -   An embodiment wherein the STD further comprises a software        application configured to display TTIs within a graphical user        interface for individual selection as a requesting TTI sent to        the TMS.    -   An embodiment wherein the STD further comprises a software        application configured to display a hierarchical tree of TTIs        within a graphical user interface for individual selection as a        requesting TTI sent to the TMS.    -   An embodiment wherein the STD further comprises a software        application configured to display graphical images associated        with a hierarchical tree of TTIs within a graphical user        interface for selection by graphical image to identify a        requesting TTI sent to the TMS.    -   An embodiment wherein the TMD comprises caller blocking        information.    -   An embodiment wherein the TMS is configured to block telephone        calls received by the TTD if the TTI matches call blocking        information contained within the TMD.    -   An embodiment wherein the TMS is configured to block telephone        calls received by the TTD if the TTI matches parental control        call blocking information contained within the TMD.    -   An embodiment wherein the TMS is configured to block telephone        calls initiated by the STD if the TTI matches call blocking        information contained within the TMD.    -   An embodiment wherein the TMS is configured to block telephone        calls initiated by the STD if the TTI matches parental control        call blocking information contained within the TMD.    -   An embodiment wherein the TMD comprises TID location blocking        information.    -   An embodiment wherein:        -   the STD is configured to communicate a current STD GPS            location to the TMS;        -   the TMS is configured to translate the GPS location into a            text string;        -   the TMS is configured to transmit the text string to the            TTD; and        -   the TTD is configured to display the text string within a            graphical display on the TTD.    -   An embodiment wherein the TMS is configured to block        transmission of the text string to the TTD if the TTI of the STD        matches TID location blocking information stored in the TMS.    -   An embodiment wherein:        -   the TTD is configured to communicate a current TTD GPS            location to the TMS;        -   the TMS is configured to translate the GPS location into a            text string;        -   the TMS is configured to transmit the text string to the            STD; and        -   the STD is configured to display the text string within a            graphical display on the STD.    -   An embodiment wherein the TMS is configured to block        transmission of the text string to the STD if the TTI of the TTD        matches TID location blocking information stored in the TMS.        One skilled in the art will recognize that other embodiments are        possible based on combinations of elements taught within the        above invention description.

Generalized Computer Usable Medium

In various alternate embodiments, the present invention may beimplemented as a computer program product for use with a computerizedcomputing system. Those skilled in the art will readily appreciate thatprograms defining the functions defined by the present invention can bewritten in any appropriate programming language and delivered to acomputer in many forms, including but not limited to: (a) informationpermanently stored on non-writeable storage media (e.g., read-onlymemory devices such as ROMs or CD-ROM disks); (b) information alterablystored on writeable storage media (e.g., floppy disks and hard drives);and/or (c) information conveyed to a computer through communicationmedia, such as a local area network, a telephone network, or a publicnetwork such as the Internet. When carrying computer readableinstructions that implement the present invention methods, such computerreadable media represent alternate embodiments of the present invention.

As generally illustrated herein, the present invention systemembodiments can incorporate a variety of computer readable media thatcomprise computer usable medium having computer readable code meansembodied therein. One skilled in the art will recognize that thesoftware associated with the various processes described herein can beembodied in a wide variety of computer accessible media from which thesoftware is loaded and activated. Pursuant to In re Beauregard, 35USPQ2d1383 (U.S. Pat. No. 5,710,578), the present invention anticipatesand includes this type of computer readable media within the scope ofthe invention. Pursuant to In re Nuijten, 500 F.3d 1346 (Fed. Cir. 2007)(U.S. patent application Ser. No. 09/211,928), the present inventionscope is limited to computer readable media wherein the media is bothtangible and non-transitory.

CONCLUSION

A telecommunications addressing system/method allowing selection of atelephone instrument device (TID) using arbitrary identifiers has beendisclosed. The system/method allows a source TID (STD) to select atarget TID (TTD) by the use of a Target Telephone Identifier (TTI) datastring rather than a traditional numeric telephone identification (NTI).This TTI is then indexed within a TTI/NTI mapping server (TMS) thatfunctions as a hierarchical and/or relational repository of TTI/NTImappings. STD/TTD communication is established by first performing alookup of the STD-selected TTI within the TMS to identify the NTI of theTTD. Once the NTI of the STD has been identified by the TMS,communication between the STD and TTD is established using the NTI viathe normal public switched telephone network (PSTN). TMS TTI lookup maybe performed via STD TID web application and/or via PSTN infrastructureinterface.

1. A telecommunications addressing system (TAS) comprising: (a) telephone mapping server (TMS); (b) telephone mapping database (TMD); (c) source telephone instrument device (STD); (d) target telephone instrument device (TTD); and (e) computer communication network (CCN); wherein said TMS is configured to store information that identifies a telephone instrument device (TID) in said TMD; said TMS is configured to locate a numeric telephone identifier (NTI) within said TMD using a target telephone identifier (TTI) data string as the locating index; said NTI permits said TID to be accessed via a public switched telephone network (PSTN); and said TMS is configured to initiate a telephone call via said PSTN between said STD and said TTD using said NTI.
 2. The telecommunications addressing system of claim 1 wherein said CCN comprises the Internet.
 3. The telecommunications addressing system of claim 1 wherein said TMS is configured to initiate said telephone call via said PSTN from said STD to said TTD.
 4. The telecommunications addressing system of claim 1 wherein said TMS is configured to initiate said telephone call via said PSTN from said TTD to said STD.
 5. The telecommunications addressing system of claim 1 wherein said CCN comprises a wireless communication network.
 6. The telecommunications addressing system of claim 1 wherein said TMS comprises a computer server contained within said PSTN.
 7. The telecommunications addressing system of claim 1 wherein said TMD comprises graphical images associated with said TTI/NTI mappings.
 8. The telecommunications addressing system of claim 1 wherein said TMD comprises call sequencing information associated with said TTI/NTI mappings.
 9. The telecommunications addressing system of claim 1 wherein said TMD comprises a hierarchical directory of TTI/NTI mappings.
 10. The telecommunications addressing system of claim 1 wherein said TMD associates a plurality of said NTIs contained within a hierarchical directory with said TTI.
 11. The telecommunications addressing system of claim 1 wherein said TMS returns said NTI based on current TTD status information contained within said TMD that is associated with said TTI.
 12. The telecommunications addressing system of claim 1 wherein said TMS transmits a tree of hierarchical directory TTI/NTI mappings to said STD in response to a TTI lookup request received from said STD.
 13. The telecommunications addressing system of claim 1 wherein said TMS is configured to communicate with said STD via a TTI lookup software application resident on said STD.
 14. The telecommunications addressing system of claim 1 wherein said TMS is configured to host a web application configured to permit configuration of said TMD via a web browser application operational on said STD.
 15. The telecommunications addressing system of claim 1 wherein said TTI comprises a data string selected from a group consisting of: data derived from a voice recognition software application resident on said STD; email address; website URL address; and hierarchical path of TTI atomic elements.
 16. The telecommunications addressing system of claim 1 wherein said TMD comprises data selected from a group consisting of: information extracted from an enterprise employee information database; information obtained by scanning metadata extracted from a website HTML file; information obtained by scanning metadata extracted from a social media website.
 17. The telecommunications addressing system of claim 1 wherein said TMS comprises a TMD editor (TME) configured to permit remote modification of records within said TMD specified by a TMD editing script generated in response to a series of change orders (TCOs) received from a telephone company or telephone standards organization.
 18. The telecommunications addressing system of claim 1 wherein said STD further comprises a software application configured to display TTIs within a graphical user interface for individual selection as a requesting TTI sent to said TMS.
 19. The telecommunications addressing system of claim 1 wherein said STD further comprises a software application configured to display a hierarchical tree of TTIs within a graphical user interface for individual selection as a requesting TTI sent to said TMS.
 20. The telecommunications addressing system of claim 1 wherein said STD further comprises a software application configured to display graphical images associated with a hierarchical tree of TTIs within a graphical user interface for selection by graphical image to identify a requesting TTI sent to said TMS.
 21. The telecommunications addressing system of claim 1 wherein said TMD comprises caller blocking information.
 22. The telecommunications addressing system of claim 1 wherein said TMS is configured to block telephone calls received by said TTD if said TTI matches call blocking information contained within said TMD.
 23. The telecommunications addressing system of claim 1 wherein said TMS is configured to block telephone calls received by said TTD if said TTI matches parental control call blocking information contained within said TMD.
 24. The telecommunications addressing system of claim 1 wherein said TMS is configured to block telephone calls initiated by said STD if said TTI matches call blocking information contained within said TMD.
 25. The telecommunications addressing system of claim 1 wherein said TMS is configured to block telephone calls initiated by said STD if said TTI matches parental control call blocking information contained within said TMD.
 26. The telecommunications addressing system of claim 1 wherein said TMD comprises TID location blocking information.
 27. The telecommunications addressing system of claim 1 wherein: said STD is configured to communicate a current STD GPS location to said TMS; said TMS is configured to translate said GPS location into a text string; said TMS is configured to transmit said text string to said TTD; and said TTD is configured to display said text string within a graphical display on said TTD.
 28. The telecommunications addressing system of claim 27 wherein said TMS is configured to block transmission of said text string to said TTD if the TTI of said STD matches TID location blocking information stored in said TMS.
 29. The telecommunications addressing system of claim 1 wherein: said TTD is configured to communicate a current TTD GPS location to said TMS; said TMS is configured to translate said GPS location into a text string; said TMS is configured to transmit said text string to said STD; and said STD is configured to display said text string within a graphical display on said STD.
 30. The telecommunications addressing system of claim 29 wherein said TMS is configured to block transmission of said text string to said STD if the TTI of said TTD matches TID location blocking information stored in said TMS. 